Build faild on heroku

[eliavmaman]

remote:        gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:240:12)
remote:        gyp ERR! System Linux 4.4.0-1027-aws
remote:        gyp ERR! command "/tmp/build_50d0e12a9f0abbf48d836666efa6a597/.heroku/node/bin/node" "/tmp/build_50d0e12a9f0abbf48d836666efa6a597/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
remote:        gyp ERR! cwd /tmp/build_50d0e12a9f0abbf48d836666efa6a597/node_modules/node-sass
remote:        gyp ERR! node -v v10.11.0
remote:        gyp ERR! node-gyp -v v3.6.2
remote:        gyp ERR! not ok
remote:        Build failed with error code: 1
remote:        npm ERR! code ELIFECYCLE
remote:        npm ERR! errno 1
remote:        npm ERR! node-sass@4.5.3 postinstall: `node scripts/build.js`
remote:        npm ERR! Exit status 1
remote:        npm ERR!
remote:        npm ERR! Failed at the node-sass@4.5.3 postinstall script.
remote:        npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
remote:        
remote:        npm ERR! A complete log of this run can be found in:
remote:        npm ERR!     /tmp/npmcache.tybah/_logs/2018-09-25T14_29_53_412Z-debug.log
remote: 
remote: -----> Build failed
remote:        
remote:        We're sorry this build is failing! You can troubleshoot common issues here:
remote:        https://devcenter.heroku.com/articles/troubleshooting-node-deploys
remote:        
remote:        Some possible problems:
remote:        
remote:        - Dangerous semver range (>) in engines.node
remote:        https://devcenter.heroku.com/articles/nodejs-support#specifying-a-node-js-version
remote:        
remote:        Love,
remote:        Heroku

Look like node-sass makes the problem Any idea?

[lirantal]

@eliavmaman maintenance on the project has stalled. if you're able to pick up maintenance on the project, I'll be happy to add you as a contributor

[RahulChakravarthy]

@eliavmaman did you try removing the '>' from package.json -> I changed it from: "engines": { "node": ">=6.10.0", "npm": ">=3.10.8" }, to: "engines": { "node": "6.10.0", "npm": "3.10.8" }, and it started building for me. See this for more info -> https://github.com/meanjs/mean/issues/1928

[uthmanq]

Lots of problems seem to stem from gulp dependencies. I removed gulp dependencies and instead use just "start: "npm start" for heroku. Setting the node environment to development worked like a charm.