-
Notifications
You must be signed in to change notification settings - Fork 614
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
npm run webpack-production throws an exception #196
Comments
i see also all the bug deprectated list and i'm thinking this project is no more maintain and is now dead. |
What a shame. This could have been something. |
Is it a dead project? I have to start coding in react and better to know before waste time with a closed ide project |
microsoft/monaco-editor-webpack-plugin#92 Follow instructions in above thread. |
I manage to solve this issue: 1 -) resolve the peer depencency conflic between monaco-editor and monaco-editor-webpack-plugin 2 -) install spawn-sync package using npm 3 -) install ttf-loader package using npm 4 -) change webpack.config.js file, search this section: and change it for this one: plugins: [ 5 -) add the following loader module config into webpack.config.js, goes into the modules->rules array { 6 -) run npm install
please tellme if these steps worked for you. |
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/usr/local/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'webpack-production'
1 verbose cli ]
2 info using npm@6.14.5
3 info using node@v14.5.0
4 verbose run-script [
4 verbose run-script 'prewebpack-production',
4 verbose run-script 'webpack-production',
4 verbose run-script 'postwebpack-production'
4 verbose run-script ]
5 info lifecycle reactide@3.0.0
prewebpack-production: reactide@3.0.0webpack-production: reactide@3.0.06 info lifecycle reactide@3.0.0
7 verbose lifecycle reactide@3.0.0
webpack-production: unsafe-perm in lifecycle truewebpack-production: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/ketans/projects/reactide/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/mnt/c/Program Files/WindowsApps/CanonicalGroupLimited.UbuntuonWindows_2004.2020.424.0_x64__79rhkp1fndgsc:/mnt/c/Python38/Scripts/:/mnt/c/Python38/:/mnt/c/Program Files (x86)/Common Files/Intel/Shared Libraries/redist/intel64/compiler:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/iCLS/:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/iCLS/:/mnt/c/Windows/system32:/mnt/c/Windows:/mnt/c/Windows/System32/Wbem:/mnt/c/Windows/System32/WindowsPowerShell/v1.0/:/mnt/c/Windows/System32/OpenSSH/:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/DAL:/mnt/c/Program Files (x86)/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files/Intel/Intel(R) Management Engine Components/IPT:/mnt/c/Program Files (x86)/NVIDIA Corporation/PhysX/Common:/mnt/c/WINDOWS/system32:/mnt/c/WINDOWS:/mnt/c/WINDOWS/System32/Wbem:/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/:/mnt/c/WINDOWS/System32/OpenSSH/:/mnt/c/Program Files (x86)/Calibre2/:/mnt/c/ProgramData/chocolatey/bin:/mnt/c/Program Files/nodejs/:/mnt/c/Program Files/Git/cmd:/mnt/c/Users/windo/AppData/Local/Programs/Python/Python38-32/Scripts/:/mnt/c/Users/windo/AppData/Local/Programs/Python/Python38-32/:/mnt/c/Users/windo/AppData/Local/Microsoft/WindowsApps:/mnt/c/Program Files/JetBrains/PyCharm 2019.3.3/bin:/mnt/c/Users/windo/AppData/Local/Programs/Microsoft VS Code/bin:/mnt/c/Users/windo/AppData/Local/JetBrains/jdk8/jre/bin:/mnt/c/tools/dart-sdk/bin:/mnt/c/tools/flutter/bin:/mnt/c/Users/windo/AppData/Roaming/Pub/Cache/bin:/mnt/c/tools/flutter/:/mnt/c/Users/windo/AppData/Roaming/npm:/mnt/c/Users/windo/AppData/Local/GitHubDesktop/bin:/mnt/c/Python27/:/mnt/c/Python27/Scripts/8 verbose lifecycle reactide@3.0.0
9 verbose lifecycle reactide@3.0.0
webpack-production: CWD: /home/ketans/projects/reactidewebpack-production: Args: [ '-c', 'webpack --mode production' ]10 silly lifecycle reactide@3.0.0
11 silly lifecycle reactide@3.0.0
webpack-production: Returned: code: 1 signal: nullwebpack-production: Failed to exec webpack-production script12 info lifecycle reactide@3.0.0
13 verbose stack Error: reactide@3.0.0 webpack-production:
webpack --mode production
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1051:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid reactide@3.0.0
15 verbose cwd /home/ketans/projects/reactide
16 verbose Linux 4.4.0-19041-Microsoft
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "webpack-production"
18 verbose node v14.5.0
19 verbose npm v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error reactide@3.0.0 webpack-production:
webpack --mode production
22 error Exit status 1
23 error Failed at the reactide@3.0.0 webpack-production script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
The text was updated successfully, but these errors were encountered: