The two gulp commands usually fail with "bash: gulp: command not found" for me. We could have users specify the file to node_modules/gulp/bin/gulp.js when running these commands, but that seems like it could easily break, and is a lot of typing. :-)
Maybe we could add something like this to package.json:
"scripts": {
"gulp-bundle": "gulp bundle"
}
And then users could run `npm run gulp-bundle` and not have to worry about what binaries happen to be in their PATH.
And is there any purpose to the `gulp --tasks-simple` line, other than to confirm gulp installed correctly?
One issue with the install instructions in the README:
30 $ cd ui
31 $ npm install
32 $ gulp --tasks-simple
33 $ gulp bundle
The two gulp commands usually fail with "bash: gulp: command not found" for me. We could have users specify the file to node_modules/ gulp/bin/ gulp.js when running these commands, but that seems like it could easily break, and is a lot of typing. :-)
Maybe we could add something like this to package.json:
"scripts": { gulp-bundle" : "gulp bundle"
"
}
And then users could run `npm run gulp-bundle` and not have to worry about what binaries happen to be in their PATH.
And is there any purpose to the `gulp --tasks-simple` line, other than to confirm gulp installed correctly?