I'm getting the following error:
5065 verbose linkBins sse4_crc32#4.1.1
5066 verbose linkMans sse4_crc32#4.1.1
5067 verbose rebuildBundles sse4_crc32#4.1.1
5068 verbose rebuildBundles [ 'bindings', 'nan' ]
5069 info install sse4_crc32#4.1.1
5070 verbose unsafe-perm in lifecycle false
5071 info sse4_crc32#4.1.1 Failed to exec install script
5072 verbose stack Error: sse4_crc32#4.1.1 install: `node-gyp rebuild`
5072 verbose stack Exit status 1
5072 verbose stack at EventEmitter.<anonymous> (/opt/elasticbeanstalk/node-install/node-v4.2.1-linux-x64/lib/node_modules/npm/lib/utils/lifecycle.js:214:16)
5072 verbose stack at emitTwo (events.js:87:13)
5072 verbose stack at EventEmitter.emit (events.js:172:7)
5072 verbose stack at ChildProcess.<anonymous> (/opt/elasticbeanstalk/node-install/node-v4.2.1-linux-x64/lib/node_modules/npm/lib/utils/spawn.js:24:14)
5072 verbose stack at emitTwo (events.js:87:13)
5072 verbose stack at ChildProcess.emit (events.js:172:7)
5072 verbose stack at maybeClose (internal/child_process.js:818:16)
5072 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
5073 verbose pkgid sse4_crc32#4.1.1
5074 verbose cwd /tmp/deployment/application
5075 error Linux 4.1.10-17.31.amzn1.x86_64
5076 error argv "/opt/elasticbeanstalk/node-install/node-v4.2.1-linux-x64/bin/node" "/opt/elasticbeanstalk/node-install/node-v4.2.1-linux-x64/bin/npm" "--production" "rebuild"
5077 error node v4.2.1
5078 error npm v2.14.7
5079 error code ELIFECYCLE
5080 error sse4_crc32#4.1.1 install: `node-gyp rebuild`
5080 error Exit status 1
5081 error Failed at the sse4_crc32#4.1.1 install script 'node-gyp rebuild'.
5081 error This is most likely a problem with the sse4_crc32 package,
5081 error not with npm itself.
5081 error Tell the author that this fails on your system:
5081 error node-gyp rebuild
5081 error You can get their info via:
5081 error npm owner ls sse4_crc32
5081 error There is likely additional logging output above.
5082 verbose exit [ 1, true ]
package.json
{
"name": "application-name",
"version": "0.0.1",
"private": true,
"scripts": {
"test": "mocha"
},
"dependencies": {
"async": "^0.8.0",
"aws-sdk": "^2.2.21",
"bcrypt-nodejs": "0.0.3",
"body-parser": "^1.0.2",
"config": "^1.16.0",
"cors": "^2.7.1",
"crypto": "0.0.3",
"crypto-js": "^3.1.5",
"debug": "^0.7.4",
"express": "^4.0.0",
"express-jwt": "^0.4.0",
"express-validator": "^2.3.0",
"fs": "0.0.2",
"jade": "^1.3.1",
"jsonwebtoken": "^5.0.0",
"mongoose": "^4.0.0",
"morgan": "^1.0.1",
"multer": "^1.1.0",
"nodemailer": "^1.8.0",
"os-shim": "^0.1.3",
"prompt": "^0.2.14",
"request": "^2.67.0",
"validator": "^3.22.1"
},
"devDependencies": {
"chai": "^1.9.1",
"chance": "^0.5.9",
"mocha": "^1.18.2",
"node-inspector": "^0.12.3",
"supertest": "^0.13.0"
}
}
Errors thrown in EB console:
2015-12-05 08:44:49 UTC+0700 ERROR During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.
2015-12-05 08:44:49 UTC+0700 ERROR Failed to deploy application.
2015-12-05 08:44:49 UTC+0700 ERROR Unsuccessful command execution on instance id(s) 'i-65c4d5dc'. Aborting the operation.
2015-12-05 08:44:49 UTC+0700 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1].
2015-12-05 08:44:49 UTC+0700 ERROR [Instance: i-65c4d5dc] Command failed on instance. Return code: 1 Output: (TRUNCATED)..."/opt/elasticbeanstalk/containerfiles/ebnode.py", line 166, in npm_install raise e subprocess.CalledProcessError: Command '['/opt/elasticbeanstalk/node-install/node-v4.2.1-linux-x64/bin/npm', '--production', 'rebuild']' returned non-zero exit status 1. Hook /opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.
Here's the .ebextensions/config.config I'm trying:
packages:
yum:
gcc: []
make: []
openssl-devel: []
libxml2: []
libxml2-devel: []
files:
"/opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh" :
mode: "000775"
owner: root
group: root
content: |
#!/bin/bash
function error_exit
{
eventHelper.py --msg "$1" --severity ERROR
exit $2
}
export HOME=/home/ec2-user # ADDED EXPORT COMMAND
echo "export home" # JUST FOR REMARK
OUT=$(/opt/elasticbeanstalk/containerfiles/ebnode.py --action npm- install 2>&1) || error_exit "Failed to run npm install. $OUT" $?
echo $OUT
It looks like the error is coming from node-gyp or sse4_crc32.
Is there some config I should be using in an .ebextensions file to overcome this please?
Thanks
Solved.
The EB config file fixed it. My path to it was .ebextensions/config.config
packages:
yum:
gcc: []
make: []
openssl-devel: []
libxml2: []
libxml2-devel: []
files:
"/opt/elasticbeanstalk/hooks/appdeploy/pre/50npm.sh" :
mode: "000775"
owner: root
group: root
content: |
#!/bin/bash
function error_exit
{
eventHelper.py --msg "$1" --severity ERROR
exit $2
}
export HOME=/home/ec2-user # ADDED EXPORT COMMAND
echo "export home" # JUST FOR REMARK
OUT=$(/opt/elasticbeanstalk/containerfiles/ebnode.py --action npm- install 2>&1) || error_exit "Failed to run npm install. $OUT" $?
echo $OUT
The home directory in the NPM task seemed to do the job.
Something key that held me back also - zipping the project in the Mac GUI will not zip hidden files. This can be overcome by doing it in the command line using:
zip -r archive_name.zip * .*
Related
Failed to compile.
./assets/images/cross.png
CompileError: AsyncCompile: Wasm decoding failed: mutable globals cannot be exported #+482
> Build error occurred
Error: > Build failed because of webpack errors
at nextBuildSpan.traceAsyncFn (/var/app/kv-v2/node_modules/next/dist/build/index.js:15:924)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! kv-update#1.7.3 build: `next build`
npm ERR! Exit status 1
I am getting this error when trying to npm run build on my ubuntu server it was working fine previously and it is still compiling fine on my localhost windows machine so to be sure it was not due to my code I reverted to the old copy from Github that was working but its still getting the same error when compiling. I did remove the node_modules and reinstalled.
I tried Googling and there were around 10 articles of this none of them were able to fix my issue. Please help me. Thank you. This is the full log file.
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.14.4
3 info using node#v10.19.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle kv-update#1.7.3~prebuild: kv-update#1.7.3
6 info lifecycle kv-update#1.7.3~build: kv-update#1.7.3
7 verbose lifecycle kv-update#1.7.3~build: unsafe-perm in lifecycle true
8 verbose lifecycle kv-update#1.7.3~build: PATH: /usr/share/npm/node_modules/npm-lifecycle/node-gyp-bin:/var/app/kv-v2/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
9 verbose lifecycle kv-update#1.7.3~build: CWD: /var/app/kv-v2
10 silly lifecycle kv-update#1.7.3~build: Args: [ '-c', 'next build' ]
11 silly lifecycle kv-update#1.7.3~build: Returned: code: 1 signal: null
12 info lifecycle kv-update#1.7.3~build: Failed to exec build script
13 verbose stack Error: kv-update#1.7.3 build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/share/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid kv-update#1.7.3
15 verbose cwd /var/app/kv-v2
16 verbose Linux 5.4.0-109-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v10.19.0
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error kv-update#1.7.3 build: `next build`
22 error Exit status 1
23 error Failed at the kv-update#1.7.3 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
My package.json file
{
"name": "kvr",
"version": "1.7.3",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start -p 4000",
"lint": "next lint"
},
"dependencies": {
"#notbaldrick/react-crossfade-carousel": "^1.0.4",
"babel-plugin-styled-components": "^1.13.1",
"fathom-client": "^3.1.0",
"jsonp": "^0.2.1",
"next": "11.0.1",
"npm": "^6.14.4",
"react": "17.0.2",
"react-device-detect": "^1.17.0",
"react-dom": "17.0.2",
"react-facebook-pixel": "^1.0.4",
"react-img-carousel": "^2.1.1",
"react-responsive-carousel": "^3.2.19",
"react-transition-group": "^4.4.2",
"styled-components": "^5.3.0"
},
"devDependencies": {
"babel-plugin-styled-components": "^1.13.1",
"eslint": "7.30.0",
"eslint-config-next": "11.0.1"
}
}
I did fix it by removing the cross.png file converting it to cross.jpg and updated the code everything it is importing this file. Strange bug It seems.
I need to use react-testing-library for unit test cases in nextjs application. In react applications which was created using create react app, I used to just call npm run test and the test scripts run.
But in nexJs while trying to calling npm run test if gives errors.
The nextjs application was created using create-next-app.
I installed react-testing-library manually into nextjs application.
I installed:
#testing-library/react
#testing-library/jest-dom
#testing-library/user-event
jest
babel-jest
And in package.js added the test script:
"test": "jest"
package.json:
{
"name": "thestobook",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"test": "jest"
},
"dependencies": {
"#emotion/react": "^11.7.1",
"#emotion/styled": "^11.6.0",
"#material-ui/core": "^4.12.3",
"#material-ui/icons": "^4.11.2",
"#mui/icons-material": "^5.3.1",
"#mui/material": "^5.4.0",
"#testing-library/jest-dom": "^5.16.4",
"#testing-library/react": "^13.2.0",
"#testing-library/user-event": "^14.2.0",
"#types/axios": "^0.14.0",
"axios": "^0.25.0",
"babel-jest": "^28.1.0",
"bcryptjs": "^2.4.3",
"formik": "^2.2.9",
"jest": "^28.1.0",
"js-cookie": "^3.0.1",
"jsonwebtoken": "^8.5.1",
"mongoose": "^6.2.0",
"next": "12.0.10",
"react": "17.0.2",
"react-dom": "17.0.2",
"react-outside-click-handler": "^1.3.0",
"react-slugify": "^2.1.0",
"react-test-renderer": "^18.1.0",
"react-toastify": "^8.2.0",
"recoil": "^0.6.1",
"sass": "^1.49.4",
"slugify": "^1.6.5",
"use-image-color": "0.0.9",
"yup": "^0.32.11"
},
"devDependencies": {
"#types/node": "17.0.14",
"#types/react": "17.0.38",
"eslint": "8.8.0",
"eslint-config-next": "12.0.10",
"typescript": "4.5.5"
}
}
After installation, Created jest.config.js:
module.exports = {
setupFilesAfterEnv: ["./jest.setup.js"],
};
also created jest.setup.js:
import "#testing-library/jest-dom";
test file created in __ test __ folder --> ComponentName.test.js
import { render, screen } from "#testing-library/react";
import Profile from "../Profile";
it("should be same as the text passed", () => {
render(<Profile />);
const textElement = screen.getByText(/explore/i);
expect(textElement).toBeInTheDocument();
});
While npm run test, It runs the test but after that gives error.
Error in terminal:
Test Suites: 1 failed, 1 total
Tests: 0 total
Snapshots: 0 total
Time: 0.343 s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! thestobook# test: `jest`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the thestobook# test 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/saikrishnadas/.npm/_logs/2022-05-25T09_49_40_372Z-debug.log
Complete Error Log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'test' ]
2 info using npm#6.14.13
3 info using node#v14.17.1
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle thestobook#~pretest: thestobook#
6 info lifecycle thestobook#~test: thestobook#
7 verbose lifecycle thestobook#~test: unsafe-perm in lifecycle true
8 verbose lifecycle thestobook#~test: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/saikrishnadas/thestobook/thestobook/node_modules/.bin:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/homebrew/bin:/opt/homebrew/sbin
9 verbose lifecycle thestobook#~test: CWD: /Users/saikrishnadas/sai-learn/thestobook/thestobook
10 silly lifecycle thestobook#~test: Args: [ '-c', 'jest' ]
11 silly lifecycle thestobook#~test: Returned: code: 1 signal: null
12 info lifecycle thestobook#~test: Failed to exec test script
13 verbose stack Error: thestobook# test: `jest`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:375:28)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:375:28)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid thestobook#
15 verbose cwd /Users/saikrishnadas/thestobook/thestobook
16 verbose Darwin 21.1.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "test"
18 verbose node v14.17.1
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 1
22 error thestobook# test: `jest`
22 error Exit status 1
23 error Failed at the thestobook# test script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I have on local Windows node v8.12.0 and npm v6.4.1. On the server I have node v11.10.0 and npm v6.7.0.
I replaced project in server with backup on local machine, but when I type npm start I have 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-14T05_41_00_295Z-debug.log
Is it possible that project does not start on server due to conflict of node version? If yes, should I upgrade node on local or downgrade node on server?
P.S. I think chmod -R 777 will NOT solve problem, because other files on server has the same rights and they start with no problem.
P.P.S. there is my package.json file if it`s needed
{
"name": "manager-polling-app-client",
"version": "0.1.0",
"private": true,
"dependencies": {
"#material-ui/core": "^3.9.3",
"ajv": "^6.9.1",
"ajv-keywords": "^3.4.1",
"antd": "^3.20.0",
"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.2.0",
"react-awesome-modal": "^2.0.5",
"react-data-export": "^0.5.0",
"react-dom": "^16.2.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.P.P.S. Log file
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ]
2 info using npm#6.7.0
3 info using node#v11.10.0
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle manager-polling-app-client#0.1.0~prestart: manager-polling-app- client#0.1.0
6 info lifecycle manager-polling-app-client#0.1.0~start: manager-polling-app-cli ent#0.1.0
7 verbose lifecycle manager-polling-app-client#0.1.0~start: unsafe-perm in lifec ycle true
8 verbose lifecycle manager-polling-app-client#0.1.0~start: PATH: /usr/local/lib /node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/root/mybpm/manager-po lling-app-client/node_modules/.bin:/usr/lib/jvm/java-8-openjdk-amd64/bin:/usr/lo cal/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/game s:/snap/bin
9 verbose lifecycle manager-polling-app-client#0.1.0~start: CWD: /root/mybpm/man ager-polling-app-client
10 silly lifecycle manager-polling-app-client#0.1.0~start: Args: [ '-c', 'react- app-rewired start' ]
11 silly lifecycle manager-polling-app-client#0.1.0~start: Returned: code: 126 signal: null
12 info lifecycle manager-polling-app-client#0.1.0~start: Failed to exec start s cript
13 verbose stack Error: manager-polling-app-client#0.1.0 start: `react-app-rewir ed start`
13 verbose stack Exit status 126
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/np m/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:197:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/np m/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:197:13)
13 verbose stack at maybeClose (internal/child_process.js:984:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_proc ess.js:265:5)
14 verbose pkgid manager-polling-app-client#0.1.0
15 verbose cwd /root/mybpm/manager-polling-app-client
16 verbose Linux 4.4.0-135-generic
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "start"
18 verbose node v11.10.0
19 verbose npm v6.7.0
20 error code ELIFECYCLE
21 error errno 126
22 error manager-polling-app-client#0.1.0 start: `react-app-rewired start`
22 error Exit status 126
23 error Failed at the manager-polling-app-client#0.1.0 start script.
23 error This is probably not a problem with npm. There is likely additional log
I am having difficulty getting to the bottom of this npm error I am receiving after my npm run build script executes. The error in the terminal is as follows:
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! vincent-site#1.0.0 build: `webpack --mode production`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the vincent-site#1.0.0 build 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/vincentcastelli/.npm/_logs/2018-11-10T20_27_41_388Z-debug.
Not very descriptive. I am using the most recent npm version at the time of writing this (6.4.1) and the most recent node (11.1.0). I am also using Babel 7 with Webpack 4 for my compiling. I have tried a few things so far.
I have tried the following steps when using both the recent version of npm/node and older versions:
npm cache clean --force
delete node_modules by $ rm -rf node_modules folder
npm install
Still receiving the error.
My log output:
0 info it worked if it ends with ok
1 verbose cli [ '/Users/vincentcastelli/.nvm/versions/node/v11.1.0/bin/node',
1 verbose cli '/Users/vincentcastelli/.nvm/versions/node/v11.1.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'build' ]
2 info using npm#6.4.1
3 info using node#v11.1.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle vincent-site#1.0.0~prebuild: vincent-site#1.0.0
6 info lifecycle vincent-site#1.0.0~build: vincent-site#1.0.0
7 verbose lifecycle vincent-site#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle vincent-site#1.0.0~build: PATH: /Users/vincentcastelli/.nvm/versions/node/v11.1.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/vincentcastelli/Documents/02_Projects/vincent-site/node_modules/.bin:/Users/vincentcastelli/.nvm/versions/node/v11.1.0/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/Frameworks/Mono.framework/Versions/Current/Commands
9 verbose lifecycle vincent-site#1.0.0~build: CWD: /Users/vincentcastelli/Documents/02_Projects/vincent-site
10 silly lifecycle vincent-site#1.0.0~build: Args: [ '-c', 'webpack --mode production' ]
11 silly lifecycle vincent-site#1.0.0~build: Returned: code: 2 signal: null
12 info lifecycle vincent-site#1.0.0~build: Failed to exec build script
13 verbose stack Error: vincent-site#1.0.0 build: `webpack --mode production`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/Users/vincentcastelli/.nvm/versions/node/v11.1.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
13 verbose stack at EventEmitter.emit (events.js:182:13)
13 verbose stack at ChildProcess.<anonymous> (/Users/vincentcastelli/.nvm/versions/node/v11.1.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:182:13)
13 verbose stack at maybeClose (internal/child_process.js:970:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:257:5)
14 verbose pkgid vincent-site#1.0.0
15 verbose cwd /Users/vincentcastelli/Documents/02_Projects/vincent-site
16 verbose Darwin 18.0.0
17 verbose argv "/Users/vincentcastelli/.nvm/versions/node/v11.1.0/bin/node" "/Users/vincentcastelli/.nvm/versions/node/v11.1.0/bin/npm" "run" "build"
18 verbose node v11.1.0
19 verbose npm v6.4.1
20 error code ELIFECYCLE
21 error errno 2
22 error vincent-site#1.0.0 build: `webpack --mode production`
22 error Exit status 2
23 error Failed at the vincent-site#1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
My package.json:
}
"scripts": {
"start": "node server.js",
"build": "webpack --mode production"
},
"dependencies": {
"body-parser": "^1.18.3",
"express": "^4.16.3",
"prop-types": "^15.6.1",
"react": "^16.5.2",
"react-dom": "^16.5.2",
"react-router-dom": "^4.3.1"
},
"engines": {
"node": "10.13.0"
},
"babel": {
"presets": [
"#babel/preset-env",
"#babel/react"
],
"plugins": [
"#babel/proposal-class-properties"
]
},
"eslintConfig": {
"extends": "airbnb",
"parser": "babel-eslint"
},
"devDependencies": {
"#babel/core": "^7.1.5",
"#babel/plugin-proposal-class-properties": "^7.1.0",
"#babel/plugin-proposal-object-rest-spread": "^7.0.0",
"#babel/preset-env": "^7.1.5",
"#babel/preset-react": "^7.0.0",
"babel-eslint": "^10.0.1",
"babel-loader": "^8.0.4",
"css-loader": "^1.0.1",
"eslint": "^5.9.0",
"eslint-config-airbnb": "^17.1.0",
"eslint-loader": "^2.1.1",
"eslint-plugin-ejs": "0.0.2",
"eslint-plugin-import": "^2.14.0",
"eslint-plugin-jsx-a11y": "^6.1.2",
"eslint-plugin-react": "^7.11.1",
"file-loader": "^2.0.0",
"html-loader": "^0.5.5",
"html-webpack-plugin": "^3.2.0",
"node-sass": "^4.10.0",
"sass-loader": "^7.1.0",
"style-loader": "^0.23.1",
"webpack": "^4.25.1",
"webpack-cli": "^3.1.2"
}
}
My webpack config:
const path = require('path');
const HtmlWebPackPlugin = require("html-webpack-plugin");
const distDir = path.join(__dirname, '/dist');
const srcDir = path.join(__dirname, '/src');
module.exports = {
entry: `${srcDir}/index.jsx`,
output: {
path: `${distDir}`,
filename: 'bundle.js',
},
module: {
rules: [
{
test: /\.(js|jsx)$/,
exclude: /(node_modules|bower_components)/,
use: ['babel-loader', 'eslint-loader'],
},
{
test: /\.html$/,
use: [
{
loader: "html-loader"
}
]
},
{
test: /\.scss$/,
use: [
"style-loader",
"css-loader",
"sass-loader"
]
},
{
test: /\.(jpg|mp4|ogv|webm)$/,
use: 'file-loader',
},
],
},
plugins: [
new HtmlWebPackPlugin({
template: "./dist/index.html",
filename: "./index.html"
})
],
resolve: { extensions: ['*', '.js', '.jsx'] },
devtool: 'cheap-eval-source-map',
};
I feel that the issue stems from a package versioning incompatibility but isolating the issue has been challenging. Thank you in advance for the assistance!
Step 1: $ npm cache clean --force
Step 2: delete node_modules folder
step 3: delete package-lock.json file
Step 4: npm install
To start again, $ npm run start or npm run build
This worked for me. Hopes it works for you.
I found out my CI/CD pipeline on Semaphore was running on a virtual machine without enough memory, thus it was failing and throwing me the error 😭
Check your memory wherever you are running that command
I am trying to compile files with webpack and npm for my reactJS applciation.
When I run npm start, it all goes well.
When I run npm run deploy or npm run build it does not work under a windows environment. It does work under a linux environment.
Does someone have an idea why ?
My files :
package.json
{
"license": "UNLICENSED",
"private": true,
"version": "1.0.0",
"webPath": "web/",
"nodePath": "node_modules/",
"devDependencies": {
"autoprefixer": "^6.3.1",
"exports-loader": "^0.6.2",
"grunt": "^0.4.5",
"grunt-autoprefixer": "^3.0.3",
"grunt-contrib-concat": "^0.5.1",
"grunt-contrib-cssmin": "^0.14.0",
"grunt-contrib-less": "^1.1.0",
"grunt-contrib-uglify": "^0.11.0",
"grunt-contrib-watch": "^0.6.1",
"grunt-css-url-rewrite": "^0.3.5",
"grunt-cssjoin": "^0.3.0",
"grunt-postcss": "^0.7.1",
"imports-loader": "^0.6.5",
"matchdep": "^1.0.0",
"redux-devtools": "^3.0.2",
"redux-devtools-dock-monitor": "^1.0.1",
"redux-devtools-log-monitor": "^1.0.4",
"webpack-shell-plugin": "^0.4.2"
},
"repository": {
"type": "git",
"url": ""
},
"dependencies": {
"babel-core": "^6.4.0",
"babel-loader": "^6.2.1",
"babel-plugin-transform-runtime": "^6.4.3",
"babel-polyfill": "^6.3.14",
"babel-preset-es2015": "^6.3.13",
"babel-preset-react": "^6.3.13",
"babel-preset-stage-0": "^6.3.13",
"babel-runtime": "^6.3.19",
"grunt-postcss": "^0.7.1",
"history": "^1.17.0",
"i18next": "^2.5.1",
"isomorphic-fetch": "^2.2.1",
"lodash": "^4.11.1",
"radium": "^0.16.2",
"rc-switch": "^1.4.2",
"react": "^0.14.6",
"react-dom": "^0.14.6",
"react-hot-loader": "^1.3.0",
"react-redux": "^4.1.2",
"react-router": "^1.0.3",
"react-router-redux": "^3.0.0",
"redux": "^3.1.6",
"redux-thunk": "^2.1.0",
"selfupdate": "^1.1.0",
"webpack": "^1.12.11",
"webpack-dev-server": "^1.14.1",
"whatwg-fetch": "^0.11.0"
},
"scripts": {
"start": "node webpack.dev-server.js",
"build": "webpack",
"deploy": "NODE_ENV=production webpack -p --config webpack.production.config.js"
}
}
webpack.config.js
var path = require('path');
var webpack = require('webpack');
var node_modules_dir = path.join(__dirname, 'node_modules');
var devFlagPlugin = new webpack.DefinePlugin({
__DEV__: JSON.stringify(JSON.parse(process.env.DEBUG || 'false'))
});
console.log(__dirname);
var config = {
entry: [
'babel-polyfill',
'webpack-dev-server/client?http://127.0.0.1:3000',
'webpack/hot/only-dev-server',
'./app/Resources/react/app.js'
],
output: {
path: path.join(__dirname, 'web/js'),
filename: 'bundle.js',
publicPath: 'http://127.0.0.1:3000/static/'
},
debug: true,
devtool: 'eval',
plugins: [
new webpack.HotModuleReplacementPlugin(),
new webpack.NoErrorsPlugin(),
devFlagPlugin
],
module: {
loaders: [
{
loaders: ["react-hot","babel-loader?plugins=transform-runtime&presets[]=es2015&presets[]=stage-0&presets[]=react"],
test: /\.js$/,
include: path.join(__dirname, 'app/Resources/react')
}
]
}
};
module.exports = config;
/*
new webpack.ProvidePlugin({
'fetch': 'imports?this=>global!exports?global.fetch!whatwg-fetch'
})
*/
webpack.dev-server.js
var webpack = require('webpack');
var WebpackDevServer = require('webpack-dev-server');
var config = require('./webpack.config');
new WebpackDevServer(webpack(config), {
publicPath: config.output.publicPath,
hot: true,
historyApiFallback: true,
quiet: false,
noInfo: false,
contentBase: "./assets"
}).listen(3000, 'localhost', function (err, result) {
if (err) {
console.log(err);
}
console.log('Listening at localhost:3000');
});
webpack.production.config.js
var path = require('path');
var node_modules_dir = path.resolve(__dirname, 'node_modules');
var config = {
entry: [
'babel-polyfill',
'./app/Resources/react/app.js'
],
debug: false,
output: {
path: path.join(__dirname, 'web/js'),
filename: 'bundle.js'
},
module: {
loaders: [
{
loaders: ["babel-loader?plugins=transform-runtime&presets[]=es2015&presets[]=stage-0&presets[]=react"],
test: /\.js$/,
include: path.join(__dirname, 'app/Resources/react')
}
]
},
plugins: []
};
module.exports = config;
I get the following error with npm run build
Microsoft Windows [Version 10.0.10586] (c) 2015 Microsoft Corporation.
All rights reserved.
D:\Divers\Programmation\Web\foodmeup.dev>npm run build
FoodMeUp#1.0.0 build D:\Divers\Programmation\Web\foodmeup.dev
webpack
D:\Divers\Programmation\Web\foodmeup.dev Hash: 9cb8c898ada89430aa7c
Version: webpack 1.13.1 Time: 3353ms [0] multi main 64 bytes {0}
[built]
+ 739 hidden modules
ERROR in ./app/Resources/react/components/subscription/total.js Module
not found: Error: Cannot resolve module 'lodash' in
D:\Divers\Programmation\Web\foodmeup.dev\app\Resources\react\components\subscription
# ./app/Resources/react/components/subscription/total.js 19:8-25
my total.js file :
import React from 'react';
import { connect } from 'react-redux';
import { updateSubscription } from '../../actions/subscription';
var _ = require('lodash');
...
I get the following error when I launch npm run deploy
D:\Divers\Programmation\Web\foodmeup.dev>npm run deploy
FoodMeUp#1.0.0 deploy D:\Divers\Programmation\Web\foodmeup.dev
NODE_ENV=production webpack -p --config webpack.production.config.js
'NODE_ENV' is not recognized as an internal or external command,
operable program or batch file.
npm ERR! Windows_NT 10.0.10586 npm ERR! argv
"C:\Development\nodejs\node.exe"
"C:\Development\nodejs\node_modules\npm\bin\npm-cli.js" "run"
"deploy" npm ERR! node v6.2.2 npm ERR! npm v3.9.5 npm ERR! code
ELIFECYCLE npm ERR! FoodMeUp#1.0.0 deploy: NODE_ENV=production
webpack -p --config webpack.production.config.js npm ERR! Exit status
1 npm ERR! npm ERR! Failed at the FoodMeUp#1.0.0 deploy script
'NODE_ENV=production webpack -p --config
webpack.production.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 FoodMeUp package, npm ERR! not with npm
itself. npm ERR! Tell the author that this fails on your system: npm
ERR! NODE_ENV=production webpack -p --config
webpack.production.config.js npm ERR! You can get information on how
to open an issue for this project with: npm ERR! npm bugs FoodMeUp
npm ERR! Or if that isn't available, you can get their info via: npm
ERR! npm owner ls FoodMeUp npm ERR! There is likely additional
logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! D:\Divers\Programmation\Web\foodmeup.dev\npm-debug.log
and my npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'C:\\Development\\nodejs\\node.exe',
1 verbose cli 'C:\\Development\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'deploy' ]
2 info using npm#3.9.5
3 info using node#v6.2.2
4 verbose run-script [ 'predeploy', 'deploy', 'postdeploy' ]
5 info lifecycle FoodMeUp#1.0.0~predeploy: FoodMeUp#1.0.0
6 silly lifecycle FoodMeUp#1.0.0~predeploy: no script for predeploy, continuing
7 info lifecycle FoodMeUp#1.0.0~deploy: FoodMeUp#1.0.0
8 verbose lifecycle FoodMeUp#1.0.0~deploy: unsafe-perm in lifecycle true
9 verbose lifecycle FoodMeUp#1.0.0~deploy: PATH: C:\Development\nodejs\node_modules\npm\bin\node-gyp-bin;D:\Divers\Programmation\Web\foodmeup.dev\node_modules\.bin;C:\Development\nodejs;C:\img;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Development\Git\cmd;C:\Program Files (x86)\Windows Live\Shared;C:\Development\wamp\bin\php\php7.0.0;C:\Net Generation\FireFox\;C:\Development\wamp\bin\mysql\mysql5.7.9\bin;C:\Program Files (x86)\Skype\Phone\;D:\Divers\Programmation\Web\foodmeup.dev\node_modules\typescript\bin;C:\Development\nodejs\;C:\Development\ruby\bin;C:\Development\wamp\bin\php\php7.0.0;C:\Development\wamp\bin\mysql\mysql5.7.9\bin;D:\Divers\Programmation\Web\foodmeup.dev\node_modules\typescript\bin;C:\img;C:\Users\Sébastien\AppData\Roaming\npm
10 verbose lifecycle FoodMeUp#1.0.0~deploy: CWD: D:\Divers\Programmation\Web\foodmeup.dev
11 silly lifecycle FoodMeUp#1.0.0~deploy: Args: [ '/d /s /c',
11 silly lifecycle 'NODE_ENV=production webpack -p --config webpack.production.config.js' ]
12 silly lifecycle FoodMeUp#1.0.0~deploy: Returned: code: 1 signal: null
13 info lifecycle FoodMeUp#1.0.0~deploy: Failed to exec deploy script
14 verbose stack Error: FoodMeUp#1.0.0 deploy: `NODE_ENV=production webpack -p --config webpack.production.config.js`
14 verbose stack Exit status 1
14 verbose stack at EventEmitter.<anonymous> (C:\Development\nodejs\node_modules\npm\lib\utils\lifecycle.js:245:16)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at EventEmitter.emit (events.js:191:7)
14 verbose stack at ChildProcess.<anonymous> (C:\Development\nodejs\node_modules\npm\lib\utils\spawn.js:24:14)
14 verbose stack at emitTwo (events.js:106:13)
14 verbose stack at ChildProcess.emit (events.js:191:7)
14 verbose stack at maybeClose (internal/child_process.js:852:16)
14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid FoodMeUp#1.0.0
16 verbose cwd D:\Divers\Programmation\Web\foodmeup.dev
17 error Windows_NT 10.0.10586
18 error argv "C:\\Development\\nodejs\\node.exe" "C:\\Development\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "deploy"
19 error node v6.2.2
20 error npm v3.9.5
21 error code ELIFECYCLE
22 error FoodMeUp#1.0.0 deploy: `NODE_ENV=production webpack -p --config webpack.production.config.js`
22 error Exit status 1
23 error Failed at the FoodMeUp#1.0.0 deploy script 'NODE_ENV=production webpack -p --config webpack.production.config.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the FoodMeUp package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error NODE_ENV=production webpack -p --config webpack.production.config.js
23 error You can get information on how to open an issue for this project with:
23 error npm bugs FoodMeUp
23 error Or if that isn't available, you can get their info via:
23 error npm owner ls FoodMeUp
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
It looks like the configuration file is not 100% correct. See details below:
need to import 'webpack' mobile before using it (webpack.config.js),
i.e., const webpack = require('webpack');
need to import path module before using it (webpack.config.js),
i.e., const path = require('path');
devFlagPlugin is not defined
also exclude the node_modules directory in the loader
module: {
loaders: [
{
....
exclude: path.resolve(__dirname, 'node_modules/')
}
]
}
I think you have two different problems.
Lodash is missing?
Now, I'm not an expert in Webpack so somebody may point out something obvious that I don't see...but...when you say it doesn't work under Windows, have you tried it on multiple Windows systems?
If this issue is only on one system or it's a PITA to get onto a second box or whatever, try:
Delete the node_modules directory
Execute npm cache clean to be sure you'll start fresh when you reinstall
Re-install with npm i --verbose > npm-install-log.txt
If the install still doesn't work, you'll have an install log to review to see if something is failing to compile or there's some other wacky error that may not be visible after install.
NODE_ENV on Windows
The NODE_ENV=production <commands> syntax is a *nix thing but not a Windows/DOS thing.
In this case, you may find it easier to create a .bat file for this where you set the variable on the first line and call the command on the second. However, this won't work on *nix platforms so....maybe:
Create two scripts and two entries in package.json, one for each OS. If it's a simple project that's mostly maintained by hand, that's probably cool.
Create a deploy.js script, executed by node, that sets the NODE_ENV variable, calls webpack via the node api to do the work. This should be OS independent and is a single script...
You can set environment variables in a cross-platform manner by using cross-env:
"deploy": "cross-env NODE_ENV=production webpack -p --config webpack.production.config.js"