@joakimbeng Thank you for pointing out that a local install does work from npm run scripts (which adds node_modules/.bin to PATH).

Global install npm i slush slush-angular -g:

$ slush -v
[slush] 1.1.1

$ slush
[slush] Installed generators
[slush] └── angular (0.4.5)

$ slush angular
[slush] Using slushfile /Users/tmpUser/.nvm/versions/node/v0.12.9/lib/node_modules/slush-angular/slushfile.js
[18:16:11] Starting 'angular:default'...
[?] What do you want to name your AngularJS app? (tmp)

Local install npm i slush@1.0.0 slush-angular@0.4.0 --save-dev with "slush":"slush" in the scripts section of package.json:

$ npm run slush -- -v

> tmp@1.0.0 slush /Users/tmpUser/tmp/tmp
> slush "-v"

[slush] 1.0.0

$ npm run slush

> tmp@1.0.0 slush /Users/tmpUser/tmp/tmp
> slush

[slush] Installed generators
[slush] └── angular (0.4.0)

$ npm run slush angular

> tmp@1.0.0 slush /Users/tmpUser/tmp/tmp
> slush "angular"

[slush] Using slushfile /Users/tmpUser/tmp/tmp/node_modules/slush-angular/slushfile.js
[18:06:24] Starting 'angular:default'...
[?] What do you want to name your AngularJS app? (tmp)

I actually really like this behavior. I wonder if adding this strategy for local generators to the documentation would be enough.

NOTE: The version of npm shipped with node v0.10 doesn't support this behavior of passing arguments/options to run-scripts.

Local Slush generators? #5

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions