search

BrowserSync / recipes

Fully working project examples showing how to use BrowserSync in various ways.
651 stars 140 forks source link

grunt.sass.autoprefixer quits on npm start with:: grunt: command not found #52

Open sinkaszab opened 6 years ago

sinkaszab commented 6 years ago

Doesn't even start. After: "npm run start" will quit with the error below.

> grunt.sass.autoprefixer@1.0.0 start /Users/.../.../.../bs-recipes/recipes/grunt.sass.autoprefixer
> grunt

sh: grunt: command not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! grunt.sass.autoprefixer@1.0.0 start: `grunt`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the grunt.sass.autoprefixer@1.0.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/.../.npm/_logs/2017-11-24T13_04_08_593Z-debug.log

node version: v8.9.0 npm version: 5.5.1

0 info it worked if it ends with ok 1 verbose cli [ '/Users/.../.nvm/versions/node/v8.9.0/bin/node', 1 verbose cli '/Users/.../.nvm/versions/node/v8.9.0/bin/npm', 1 verbose cli 'run', 1 verbose cli 'start' ] 2 info using npm@5.5.1 3 info using node@v8.9.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle grunt.sass.autoprefixer@1.0.0~prestart: grunt.sass.autoprefixer@1.0.0 6 info lifecycle grunt.sass.autoprefixer@1.0.0~start: grunt.sass.autoprefixer@1.0.0 7 verbose lifecycle grunt.sass.autoprefixer@1.0.0~start: unsafe-perm in lifecycle true 8 verbose lifecycle grunt.sass.autoprefixer@1.0.0~start: PATH: /Users/.../.nvm/versions/node/v8.9.0/lib/node_modules/npm/bin/node-gyp-bin:/Users/.../.../.../bs-recipes/recipes/grunt.sass.autoprefixer/node_modules/.bin:/Users/.../node_modules/.bin:/Users/.../.nvm/versions/node/v8.9.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin 9 verbose lifecycle grunt.sass.autoprefixer@1.0.0~start: CWD: /Users/.../.../.../bs-recipes/recipes/grunt.sass.autoprefixer 10 silly lifecycle grunt.sass.autoprefixer@1.0.0~start: Args: [ '-c', 'grunt' ] 11 info lifecycle grunt.sass.autoprefixer@1.0.0~start: Failed to exec start script 12 verbose stack Error: grunt.sass.autoprefixer@1.0.0 start: grunt 12 verbose stack spawn ENOENT 12 verbose stack at ChildProcess. (/Users/.../.nvm/versions/node/v8.9.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18) 12 verbose stack at emitTwo (events.js:126:13) 12 verbose stack at ChildProcess.emit (events.js:214:7) 12 verbose stack at maybeClose (internal/child_process.js:925:16) 12 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 13 verbose pkgid grunt.sass.autoprefixer@1.0.0 14 verbose cwd /Users/.../.../.../bs-recipes/recipes/grunt.sass.autoprefixer 15 verbose Darwin 17.2.0 16 verbose argv "/Users/.../.nvm/versions/node/v8.9.0/bin/node" "/Users/.../.nvm/versions/node/v8.9.0/bin/npm" "run" "start" 17 verbose node v8.9.0 18 verbose npm v5.5.1 19 error file sh 20 error code ELIFECYCLE 21 error errno ENOENT 22 error syscall spawn 23 error grunt.sass.autoprefixer@1.0.0 start: grunt 23 error spawn ENOENT 24 error Failed at the grunt.sass.autoprefixer@1.0.0 start script. 24 error This is probably not a problem with npm. There is likely additional logging output above. 25 verbose exit [ 1, true ]

sinkaszab commented 6 years ago

I have an updated version of dependencies. It does start and run, but SASS won't get compiled. However no error is also thrown...

"devDependencies": {
    "browser-sync": "^2.18.13",
    "grunt": "^1.0.1",
    "grunt-autoprefixer": "^3.0.4",
    "grunt-browser-sync": "^2.2.0",
    "grunt-contrib-sass": "^1.0.0",
    "grunt-contrib-watch": "^1.0.0"
  }