javascript - Angular-hottowel gulp serve-build failing -
i'm runing ubuntu 14.10 64bits. node.js version 0.12.2 , npm version 2.7.4.
**this not visual studio project, rather https://github.com/johnpapa/generator-hottowel
i can't figure out one, after running either gulp serve-build
or gulp build
error:
[14:36:52] finished 'inject' after 236 ms **path-to-my-project**/node_modules/gulp-jscs/index.js:99 this.emit('error', new gutil.pluginerror('gulp-jscs', out.join('\n\n'), { ^ rangeerror: invalid string length @ array.join (native) @ destroyabletransform._flush (**path-to-my-project**/node_modules/gulp-jscs/index.js:99:62) @ destroyabletransform.<anonymous> (**path-to-my-project**/node_modules/gulp-jscs/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:135:12) @ destroyabletransform.g (events.js:199:16) @ destroyabletransform.emit (events.js:129:20) @ finishmaybe (**path-to-my-project**/node_modules/gulp-jscs/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:371:12) @ endwritable (**path-to-my-project**/node_modules/gulp-jscs/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:378:3) @ destroyabletransform.writable.end (**path-to-my-project**/node_modules/gulp-jscs/node_modules/through2/node_modules/readable-stream/lib/_stream_writable.js:356:5) @ destroyabletransform.onend (**path-to-my-project**/node_modules/gulp-jshint/node_modules/through2/node_modules/readable-stream/lib/_stream_readable.js:523:10) @ destroyabletransform.g (events.js:199:16)
i have jscs plugin sublime text 3 , can't find error in style. give me hand please?
** edit ** i've tried clearing cache , installing different versions of plugin, either displays different error, or presents same issue.
so went ahead , added try/catch block on index.js
file in plugin. allows execution of rest of gulp tasks in gulp.js
file wouldn't consider solution.
what think?
the jscs gulp plugin has nothing sublime plguin. seems plugin has error.
i can't information comes from. deleting node modules , reinstalling doing:
npm cache clear npm
helps.
Comments
Post a Comment