jpettersson/lingon-cli

Command line interface to Lingon, a static site generator.

lingon-cli's Issues

lingon help

that prints available commands, e.g.

lingon
lingon new [project name]
lingon build
lingon server
lingon version
lingon help
...

lingon new angular my-project

will create a new lingon project by cloning an angular template from github in a folder named my-project

lingon new my-project [--templatetype]

lingon new my-project # same as:
lingon new my-project --basic

# other templates
lingon new my-project --angular
lingon new my-project --react

Upgrade from lingon-cli 0.2.1 to 0.2.2 broke CSS generation

After receiving the upgrade from 0.2.1 to 0.2.2 of lingon-cli last week, the LESS to CSS generation began failing in my project. Error message was:

[ Lingon ] [Stream Error] Object has no method 'genCSS' in file undefined line no. undefined

Hardwiring lingon-cli to 0.2.1 fixes the build again.

generating new project will put the project name in the appropriate places

like in <title> and the <h1> and the angular.module('myProject', []); etc

lingon new es6 my-project

woooo

liftoff 2x / v8flags 2x released

Heya, this is just a friendly note to let you know that a new version of Liftoff and some of the dependencies commonly used in conjunction with it have been released. This release adds better support for situations where your user's configuration files are written using features behind a v8 flag (e.g. --harmony). Windows users and io.js users should see less issues if you upgrade!

Some helpful links:
https://github.com/tkellen/node-liftoff/blob/master/UPGRADING.md#100---200
https://github.com/tkellen/node-v8flags/blob/master/README.md#example
https://github.com/tkellen/node-hacker/blob/master/bin/hacker.js#L10-L14

Thanks!

lingon new my-project

will create a new lingon project by cloning a template from github in a folder named my-project

Error: ENOENT, no such file or directory

lingon new hello-there

[ Lingon CLI ] Initializing lingon project...

fs.js:695
  return binding.stat(pathModule._makeLong(path));
                 ^
Error: ENOENT, no such file or directory '/Users/abcdf/Projects/bootcamp/hello-there'
    at Object.fs.statSync (fs.js:695:18)
    at Object.files (/usr/local/lib/node_modules/lingon-cli/node_modules/node-dir/lib/paths.js:66:12)
    at Object.paths (/usr/local/lib/node_modules/lingon-cli/node_modules/node-dir/lib/paths.js:108:13)
    at ChildProcess.<anonymous> (/usr/local/lib/node_modules/lingon-cli/bin/lingon:71:11)
    at ChildProcess.emit (events.js:98:17)
    at Process.ChildProcess._handle.onexit (child_process.js:810:12)

cli magickery

what about convenience things like lingon init myproject would clone a lingon template project, or lingon init myproject --angular would clone the lingon-ng-template.

and of course a lingon --help that would display all of these options. I'm thinking a "single point of entry" and a convenient interface for new users of lingon to all the lingon awesomness.

typical scenario to set up a new lingon project.

$ npm install -g lingon-cli
$ lingon init myApp --angular
$ cd myApp
$ lingon server

of course inspired by rails, middlman etc :).

is this something we want, or not? to just lower the threshold for new users. still targeting experienced devs, just making it faster from discovering lingon to running your app locally.

/JD