After deploying node app with azure web app. An error appers about npm start. Project structure is simple app.js is like index.js.
App cant find a moongose module /helpers/simpleValidator.
I set up those variables in azure app config.
Environments variables
Logs
2022-08-21T02:25:53.042096825Z {"code":"MODULE_NOT_FOUND","level":"error","message":"Cannot find module './helpers/isSimpleValidator'\nRequire stack:\n- /home/site/wwwroot/node_modules/mongoose/lib/schematype.js\n- /home/site/wwwroot/node_modules/mongoose/lib/schema/mixed.js\n- /home/site/wwwroot/node_modules/mongoose/lib/document.js\n- /home/site/wwwroot/node_modules/mongoose/lib/index.js\n- /home/site/wwwroot/node_modules/mongoose/index.js\n- /home/site/wwwroot/models/user.js\n- /home/site/wwwroot/routes/user.js\n- /home/site/wwwroot/startup/routes.js\n- /home/site/wwwroot/app.js Cannot find module './helpers/isSimpleValidator'\nRequire stack:\n- /home/site/wwwroot/node_modules/mongoose/lib/schematype.js\n- /home/site/wwwroot/node_modules/mongoose/lib/schema/mixed.js\n- /home/site/wwwroot/node_modules/mongoose/lib/document.js\n- /home/site/wwwroot/node_modules/mongoose/lib/index.js\n- /home/site/wwwroot/node_modules/mongoose/index.js\n- /home/site/wwwroot/models/user.js\n- /home/site/wwwroot/routes/user.js\n- /home/site/wwwroot/startup/routes.js\n- /home/site/wwwroot/app.js","requireStack":["/home/site/wwwroot/node_modules/mongoose/lib/schematype.js","/home/site/wwwroot/node_modules/mongoose/lib/schema/mixed.js","/home/site/wwwroot/node_modules/mongoose/lib/document.js","/home/site/wwwroot/node_modules/mongoose/lib/index.js","/home/site/wwwroot/node_modules/mongoose/index.js","/home/site/wwwroot/models/user.js","/home/site/wwwroot/routes/user.js","/home/site/wwwroot/startup/routes.js","/home/site/wwwroot/app.js"],"stack":"Error: Cannot find module './helpers/isSimpleValidator'\nRequire stack:\n- /home/site/wwwroot/node_modules/mongoose/lib/schematype.js\n- /home/site/wwwroot/node_modules/mongoose/lib/schema/mixed.js\n- /home/site/wwwroot/node_modules/mongoose/lib/document.js\n- /home/site/wwwroot/node_modules/mongoose/lib/index.js\n- /home/site/wwwroot/node_modules/mongoose/index.js\n- /home/site/wwwroot/models/user.js\n- /home/site/wwwroot/routes/user.js\n- /home/site/wwwroot/startup/routes.js\n- /home/site/wwwroot/app.js\n at Function.Module._resolveFilename (node:internal/modules/cjs/loader:933:15)\n at Function.Module._load (node:internal/modules/cjs/loader:778:27)\n at Module.require (node:internal/modules/cjs/loader:1005:19)\n at require (node:internal/modules/cjs/helpers:102:18)\n at Object. (/home/site/wwwroot/node_modules/mongoose/lib/schematype.js:13:27)\n at Module._compile (node:internal/modules/cjs/loader:1101:14)\n at Object.Module._extensions..js (node:internal/modules/cjs/loader:1153:10)\n at Module.load (node:internal/modules/cjs/loader:981:32)\n at Function.Module._load (node:internal/modules/cjs/loader:822:12)\n at Module.require (node:internal/modules/cjs/loader:1005:19)"}
2022-08-21T02:25:53.082240581Z npm info lifecycle t******#1.0.0~start: Failed to exec start script
2022-08-21T02:25:53.120536311Z npm ERR! code ELIFECYCLE
2022-08-21T02:25:53.120575311Z npm ERR! errno 1
2022-08-21T02:25:53.120582912Z npm ERR! t******#1.0.0 start: `node app.js`
2022-08-21T02:25:53.120587512Z npm ERR! Exit status 1
2022-08-21T02:25:53.120591912Z npm ERR!
2022-08-21T02:25:53.120596112Z npm ERR! Failed at the t******#1.0.0 start script.
2022-08-21T02:25:53.120600812Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-08-21T02:25:53.213953705Z npm timing npm Completed in 18684ms
2022-08-21T02:25:53.213985605Z
2022-08-21T02:25:53.213992305Z npm ERR! A complete log of this run can be found in:
2022-08-21T02:25:53.213997205Z npm ERR! /root/.npm/_logs/2022-08-21T02_25_53_117Z-debug.log
2022-08-21T21:37:11.468408816Z npm ERR! taap#1.0.0 start: `node app.js`
2022-08-21T21:37:11.469692437Z npm ERR! Exit status 1
2022-08-21T21:37:11.476509148Z npm ERR!
2022-08-21T21:37:11.477776868Z npm ERR! Failed at the taap#1.0.0 start script.
2022-08-21T21:37:11.478919887Z npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2022-08-21T21:37:11.555158523Z npm timing npm Completed in 9802ms
2022-08-21T21:37:11.558920984Z
2022-08-21T21:37:11.558951084Z npm ERR! A complete log of this run can be found in:
2022-08-21T21:37:11.558972684Z npm ERR! /root/.npm/_logs/2022-08-21T21_37_11_479Z-debug.log
/home/LogFiles/2022_08_21_lw0sdlwk0001T3_docker.log (https://backendtaap.scm.azurewebsites.net/api/vfs/LogFiles/2022_08_21_lw0sdlwk0001T3_docker.log)
2022-08-21T04:07:01.722Z ERROR - Container backendtaap_0_4714aab5 for site backendtaap has exited, failing site start
Package.json
{
"name": "taap",
"version": "1.0.0",
"description": "",
"main": "app.js",
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1",
"start": "node app.js"
},
"engines": {
"node": ">=16.0.0"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"bcrypt": "^5.0.1",
"compression": "^1.7.4",
"config": "^3.3.7",
"cors": "^2.8.5",
"debug": "^4.3.3",
"dotenv": "^16.0.1",
"express": "^4.17.3",
"express-async-errors": "^3.1.1",
"helmet": "^5.0.2",
"joi": "^17.6.0",
"joi-objectid": "^4.0.2",
"joi-password-complexity": "^5.1.0",
"jsonwebtoken": "^8.5.1",
"lodash": "^4.17.21",
"mongoose": "^6.4.4",
"nodemon": "^2.0.15",
"swagger-jsdoc": "^6.2.1",
"swagger-parser": "^10.0.3",
"swagger-ui-express": "^4.4.0",
"winston": "^3.6.0",
"winston-mongodb": "^5.0.7"
}
}
Related
Firsty I should do npm run build then npm run install, but no matter what to type on the server I am getting this error.
sh: 1: react-app-rewired: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! errno 126
npm ERR! manager-polling-app-client#0.1.0 start: `react-app-rewired start`
npm ERR! Exit status 126
npm ERR!
npm ERR! Failed at the manager-polling-app-client#0.1.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! /root/.npm/_logs/2020-01-08T05_17_59_301Z-debug.log
NPM install is running on my local system but fails on server.
I cleaned cache, deleted node_modules and package-lock.json and re-installed them, but it didn`t worked.
My package.json
{
"name": "manager-polling-app-client",
"version": "0.1.0",
"private": true,
"dependencies": {
"#material-ui/core": "^3.9.3",
"ajv": "^6.0.0",
"ajv-keywords": "^3.2.0",
"antd": "^3.16.3",
"arui-feather": "^12.12.0",
"b64-to-blob": "^1.2.19",
"moment": "^2.22.2",
"pdfmake": "^0.1.53",
"prop-types": "^15.7.2",
"react": "^16.11.0",
"react-awesome-modal": "^2.0.5",
"react-data-export": "^0.5.0",
"react-dom": "^16.11.0",
"react-export-excel": "^0.5.3",
"react-router-dom": "^4.3.1",
"react-scripts": "1.1.1",
"react-select": "^2.4.2",
"xlsx": "^0.14.4"
},
"scripts": {
"start": "react-app-rewired start",
"build": "react-app-rewired build",
"test": "react-app-rewired test --env=jsdom",
"eject": "react-scripts eject"
},
"devDependencies": {
"babel-plugin-import": "^1.11.0",
"react-app-rewire-less": "^2.1.3",
"react-app-rewired": "^1.6.2"
}
}
P.S. I found that I can change rights with chmod -R 777, but people say it`s a bad idea. Personally, it worked on the server and I do not wanna play with rights (worry that will crash it at , i think there is another way to solve issue.
P.P.S. If here I should use yarn, then I should yarn add on local system and then permanently use yarn on server?
P.P.P.S. I am really newbee in npm and in yarn... sorry if question seems stupid
I am trying to modify a npm module and I want to include the modified module as a local dependency.
When deploying this app on hosting, I am facing a strange webpack not found problem. I managed to reproduce the problem in my local machine by removing webpack globally.
My package.json:
1) I try to include the local module in package.json dependencies:
{
"name": "parse-server-example",
"version": "1.4.0",
"description": "An example Parse API server using the parse-server module",
"main": "index.js",
"repository": {
"type": "git",
"url": "https://github.com/ParsePlatform/parse-server-example"
},
"license": "MIT",
"dependencies": {
"webpack": "2.3.3",
"express": "~4.11.x",
"kerberos": "~0.0.x",
"parse": "~1.8.0",
"parse-dashboard-simple": "./parse-dashboard-simple",
"parse-server": "*"
},
"scripts": {
"start": "node index.js"
},
"engines": {
"node": "7.6.0"
}
}
Take note that I have a local module called "./parse-dashboard-simple".
My local module's package.json:
{
"name": "parse-dashboard",
"parseDashboardFeatures": [
"Data Browser",
"Cloud Code Viewer",
"Cloud Code Jobs Viewer and Runner",
"Parse Config",
"API Console",
"Class Level Permissions Editor",
"Pointer Permissions Editor",
"Send Push Notifications",
"Logs Viewer",
"Push Status Page",
"Relation Editor"
],
"description": "The Parse Dashboard",
"keywords": [
"parse",
"dashboard"
],
"homepage": "https://github.com/ParsePlatform/parse-dashboard",
"bugs": "https://github.com/ParsePlatform/parse-dashboard/issues",
"version": "1.0.25",
"repository": {
"type": "git",
"url": "https://github.com/ParsePlatform/parse-dashboard"
},
"license": "SEE LICENSE IN LICENSE",
"files": [
"Parse-Dashboard",
"bin",
"README.md",
"LICENSE"
],
"dependencies": {
"bcryptjs": "^2.3.0",
"body-parser": "^1.15.2",
"commander": "^2.9.0",
"connect-flash": "^0.1.1",
"cookie-session": "^2.0.0-alpha.1",
"csurf": "^1.9.0",
"express": "^4.13.4",
"json-file-plus": "^3.2.0",
"package-json": "^2.3.1",
"passport": "^0.3.2",
"passport-local": "^1.0.0",
"webpack": "~1.12.0"
},
"devDependencies": {
"babel-core": "~5.8.12",
"babel-loader": "~5.3.0",
"babel-plugin-remove-proptypes": "~1.0.0",
"babel-polyfill": "^6.7.2",
"babel-runtime": "~5.8.25",
"css-loader": "~0.18.0",
"file-loader": "^0.8.5",
"history": "^2.1.2",
"http-server": "~0.8.5",
"immutable": "~3.7.5",
"immutable-devtools": "~0.0.4",
"jest-cli": "^12.0.2",
"js-beautify": "~1.5.0",
"marked": "^0.3.5",
"node-sass": "^3.7.0",
"parse": "1.6.14",
"prismjs": "~1.2.0",
"react": "^15.0.1",
"react-addons-test-utils": "^15.0.1",
"react-dnd": "~2.1.4",
"react-dnd-html5-backend": "~2.0.0",
"react-dom": "^15.0.1",
"react-router": "^2.6.0",
"request-promise": "^4.1.1",
"sass-loader": "~3.1.2",
"style-loader": "~0.12.3",
"svg-prep": "~1.0.0",
"transform-jest-deps": "^2.1.0",
"webpack": "~1.12.0"
},
"scripts": {
"dev": "node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --devtool eval-source-map --progress --watch",
"dashboard": "node ./Parse-Dashboard/index.js & webpack --config webpack/build.config.js --progress --watch",
"pig": "http-server ./PIG -p 4041 -s & webpack --config webpack/PIG.config.js --progress --watch",
"build": "NODE_ENV=production webpack --config webpack/production.config.js && webpack --config webpack/PIG.config.js",
"test": "NODE_PATH=./node_modules jest",
"generate": "node scripts/generate.js",
"prepublish": "webpack --config webpack/publish.config.js",
"start": "node ./Parse-Dashboard/index.js"
},
"bin": {
"parse-dashboard": "./bin/parse-dashboard"
},
"engines": {
"node": "7.6.0"
},
"main": "Parse-Dashboard/app.js",
"jest": {
"testPathDirs": [
"src/lib"
],
"scriptPreprocessor": "<rootDir>/testing/preprocessor.js",
"testDirectoryName": "tests",
"testFileExtensions": [
"test.js"
],
"unmockedModulePathPatterns": [
"react",
"react-dom",
"react-addons-test-utils",
"fbjs"
]
}
}
If I run "npm install" at the root level of this project, I will get this error:
npm WARN prepublish-on-install As of npm#5, `prepublish` scripts will run only for `npm publish`.
npm WARN prepublish-on-install (In npm#4 and previous versions, it also runs for `npm install`.)
npm WARN prepublish-on-install See the deprecation note in `npm help scripts` for more information.
> parse-dashboard#1.0.25 prepublish /mypath/-dashboard-advanced
> webpack --config webpack/publish.config.js
sh: webpack: command not found
npm ERR! addLocal Could not install /mypath/-dashboard-advanced
npm ERR! addLocal Could not install /mypath/-dashboard-simple
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! Darwin 16.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install"
npm ERR! node v7.6.0
npm ERR! npm v4.1.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! parse-dashboard#1.0.25 prepublish: `webpack --config webpack/publish.config.js`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the parse-dashboard#1.0.25 prepublish script 'webpack --config webpack/publish.config.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the parse-dashboard package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! webpack --config webpack/publish.config.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs parse-dashboard
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls parse-dashboard
npm ERR! There is likely additional logging output above.
So my understanding is that the webpack is needed in prepublish script but it is not found. But I have intentionally added webpack as dependencies in both root project or the local module (in both dev and production dependencies just to be safe), why is webpack still not found?
I'm able to run my scripts successfully, however, when i exit (ctrl + c) I get a loud error from the eslint, or jest jobs that were watching. Is there a means of suppressing these, as I get errors from the package themselves when the tests or linting fails
Example error:
npm ERR! Darwin 15.6.0
npm ERR! argv "/usr/local/Cellar/node/7.5.0/bin/node" "/usr/local/bin/npm" "run" "lint"
npm ERR! node v7.5.0
npm ERR! npm v4.1.2
npm ERR! code ELIFECYCLE
npm ERR! wpauth#1.0.0 lint: `esw webpack.config.* src tools --color`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the wpauth#1.0.0 lint script 'esw webpack.config.* src tools --color'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the wpauth package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! esw webpack.config.* src tools --color
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs wpauth
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls wpauth
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/gazzwi86/Sites/tokenauth/npm-debug.log
Package.json
{
"name": "wpauth",
"version": "1.0.0",
"scripts": {
"start": "npm run start:dev",
"start:dev": "npm-run-all --parallel test:watch lint:watch serve:dev open:dev",
"start:dist": "npm-run-all build open:dist serve:dist",
"prebuild": "rm -r src/main/webapp/public/secure-me && mkdir src/main/webapp/public/secure-me && npm run test && npm run lint",
"build": "webpack -p --define process.env.NODE_ENV='\"production\"' --optimize-minimize && cp ./src/ui/index.html src/main/webapp/public/secure-me/",
"lint": "esw webpack.config.* src tools --color",
"lint:watch": "npm run lint -- --watch",
"test": "jest",
"test:watch": "npm run test -- --watch",
"open:dev": "open http://localhost:8080/webpack-dev-server/",
"open:dist": "open http://localhost:8080/",
"serve:dev": "webpack-dev-server --progress --colors --content-base src/ui",
"serve:dist": "http-server src/main/webapp/public/secure-me"
},
"jest": {
"moduleNameMapper": {
"\\.(css|scss)$": "identity-obj-proxy",
"^.+\\.(gif|ttf|eot|svg|woff|woff2|ico)$": "<rootDir>/fileMock.js"
}
},
"dependencies": {
"backbone": "^1.3.3",
"jquery": "^2.2.4",
"react": "^15.4.2",
"react-dom": "^15.4.2",
"underscore": "^1.8.3"
},
"devDependencies": {
"babel-core": "^6.22.1",
"babel-eslint": "^7.1.1",
"babel-jest": "^18.0.0",
"babel-loader": "^6.2.1",
"babel-plugin-transform-class-properties": "^6.23.0",
"babel-polyfill": "^6.23.0",
"babel-preset-es2015": "^6.22.0",
"babel-preset-react": "^6.3.13",
"css-loader": "^0.26.1",
"enzyme": "^2.7.1",
"eslint": "^3.15.0",
"eslint-plugin-import": "^2.2.0",
"eslint-plugin-react": "^6.9.0",
"eslint-watch": "^2.1.14",
"http-server": "^0.9.0",
"image-webpack-loader": "^3.2.0",
"jest-cli": "^18.1.0",
"npm-run-all": "3.1.2",
"open": "0.0.5",
"react-addons-test-utils": "^15.4.2",
"sinon": "^1.17.7",
"style-loader": "^0.13.1",
"webpack": "^2.2.1",
"webpack-dev-server": "^2.3.0"
}
}
I am working on a Laravel 5.2 and Angular 2 project and I've just finished setting up angular but when running npm start, I get the following error :
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install"
npm ERR! node v4.4.7
npm ERR! npm v2.15.8
npm ERR! code ELIFECYCLE
npm ERR! # postinstall: `typings install`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the # postinstall script 'typings install'.
npm ERR! This is most likely a problem with the package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! typings install
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls
npm ERR! There is likely additional logging output above.
Can you guys help me ?
This is the content of my package.json :
{
"private": true,
"scripts": {
"prod": "gulp --production",
"dev": "gulp watch",
"start": "tsc && concurrently \"npm run tsc:w\" \"npm run lite\" ",
"lite": "lite-server",
"postinstall": "typings install",
"tsc": "tsc",
"tsc:w": "tsc -w",
"typings": "typings"
},
"devDependencies": {
"gulp": "^3.9.1",
"laravel-elixir": "^5.0.0",
"bootstrap-sass": "^3.0.0",
"concurrently": "^1.0.0",
"del": "^2.2.0"
},
"dependencies": {
"angular2": "2.0.0-beta.0",
"bootstrap-sass": "^3.0.0",
"elixir-typescript": "^1.1.2",
"es6-promise": "^3.0.2",
"es6-shim": "^0.33.3",
"laravel-elixir": "^4.0.0",
"reflect-metadata": "0.1.2",
"rxjs": "5.0.0-beta.0",
"systemjs": "0.19.6",
"zone.js": "0.5.10"
}
}
Your script is failing while trying to run 'typings install'.
1. Include typings in devDependencies
{
"devDependencies": {
"concurrently": "^2.0.0",
"lite-server": "^2.2.0",
"typescript": "^1.8.10",
"typings": "^1.0.4"
}
}
Run npm install
Create typings.json as below
{
"globalDependencies": {
"core-js": "registry:dt/core-js#0.0.0+20160602141332",
"jasmine": "registry:dt/jasmine#2.2.0+20160621224255",
"node": "registry:dt/node#6.0.0+20160807145350"
}
}
npm start
if you still having issue install typings globally
npm install typings --global
I too face this problem i do the following steps
1. i uninstall nodejs and install the latest version.
2. close the command promt and open.
3. execute npm install
4. execute npm build(not nesessery)
5. execute npm start
This works for me.
I've deleted node modules folder and installed npm using npm install command. My gulpfile.js is also perfect because other people are working perfectly with this config, even I did with this config from my another machine. But when I try to run npm run gulp from current machine it shows below errors.
Fahads-MacBook-Pro:dark-web jim$ npm run gulp
> jetaport#1.0.0 gulp /Users/jim/Documents/JETAPORT/dark-web
> gulp
module.js:327
throw err;
^
Error: Cannot find module 'gulp-shell'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/Users/jim/Documents/JETAPORT/dark-web/gulpfile.js:6:13)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "gulp"
npm ERR! node v4.4.2
npm ERR! npm v2.15.0
npm ERR! code ELIFECYCLE
npm ERR! jetaport#1.0.0 gulp: `gulp`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the jetaport#1.0.0 gulp script 'gulp'.
npm ERR! This is most likely a problem with the jetaport package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs jetaport
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!
npm ERR! npm owner ls jetaport
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/jim/Documents/JETAPORT/dark-web/npm-debug.log
And here is the package.json file
{
"name": "jetaport",
"version": "1.0.0",
"description": "The Jetaport Gulp dependencies.",
"main": "index.js",
"author": "Alexander Khost",
"repository": {
"type": "git",
"url": "git://github.com/akhost/Jetaport.git"
},
"license": "ISC",
"dependencies": {
"autoprefixer": "^6.3.1",
"babel-preset-es2015": "^6.3.13",
"babel-preset-react": "^6.3.13",
"bower": "^1.7.2",
"gulp": "^3.9.0",
"gulp-autoprefixer": "^3.1.0",
"gulp-cssnano": "^2.0.0",
"gulp-imagemin": "^2.4.0",
"gulp-postcss": "^6.0.1",
"imagemin-pngquant": "^4.2.0",
"laravel-elixir": "^5.0.0",
"pixrem": "^3.0.0",
"postcss-conditionals": "^2.0.0",
"postcss-each": "^0.9.1",
"postcss-import": "^7.1.3",
"postcss-math": "0.0.1",
"postcss-mixins": "^4.0.1",
"postcss-nested": "^1.0.0",
"postcss-reporter": "^1.3.0",
"postcss-scss": "^0.1.3",
"postcss-simple-extend": "^1.0.0",
"postcss-simple-vars": "^1.1.0",
"precss": "^1.3.0",
"yargs": "^4.4.0"
},
"bugs": {
"url": "https://github.com/akhost/Jetaport/issues"
},
"homepage": "https://github.com/akhost/Jetaport#readme",
"directories": {
"test": "tests"
},
"devDependencnpm ies": {
"gulp-notify": "^2.2.0"
},
"scripts": {
"gulp": "gulp",
"bower": "bower"
},
"devDependencies": {
"gulp": "^3.9.1"
}
}
Your package.json is missing the gulp-shell package. You have to install it with npm install --save gulp-shell (or --save-dev if you want to put it under devDependencies). Not sure how others got it working, but I'm pretty confident they have installed it themselves, similarly to what I've suggested, without the save flag, which is the reason it's missing in package.json.