You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Creating a project and linking MapStore (with file:<path-to-mapstore> or with npm link) I have the following error running npm start. Customized a little, but I don't think it is the problem.
I have this problem on linux.
Build Entries:
- Apps: {
"js/mapstore": "./js/apps/mapstore.jsx"
}
- HTML: {
"index.html": "./html/index.ejs"
}
- Themes: {
"themes/default": "./themes/default/theme.less"
}
9% setup compilation LoaderOptionsPlugin[webpack-cli] TypeError: The 'compilation' argument must be an instance of Compilation
at Function.getCompilationHooks (/home/offtherailz/work/projects/MapStore2/node_modules/webpack/lib/NormalModule.js:171:10)
at /home/offtherailz/work/projects/MapStore2/node_modules/webpack/lib/LoaderOptionsPlugin.js:43:17
at Hook.eval [as call] (eval at create (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:19:10), <anonymous>:198:1)
at Hook.CALL_DELEGATE [as _call] (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/node_modules/tapable/lib/Hook.js:14:14)
at Compiler.newCompilation (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Compiler.js:943:26)
at /home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Compiler.js:984:29
at Hook.eval [as callAsync] (eval at create (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:22:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/node_modules/tapable/lib/Hook.js:18:14)
at Compiler.compile (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Compiler.js:979:28)
at /home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Watching.js:112:19
at Hook.eval [as callAsync] (eval at create (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:34:1)
at Hook.CALL_ASYNC_DELEGATE [as _callAsync] (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/node_modules/tapable/lib/Hook.js:18:14)
at run (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Watching.js:66:33)
at Watching._go (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Watching.js:123:4)
at /home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Watching.js:57:9
at Compiler.readRecords (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Compiler.js:821:11)
at new Watching (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Watching.js:54:17)
at Compiler.watch (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack/lib/Compiler.js:362:19)
at wdm (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack-dev-middleware/index.js:41:33)
at Server.setupDevMiddleware (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack-dev-server/lib/Server.js:207:23)
at new Server (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/webpack-dev-server/lib/Server.js:118:10)
at Object.startDevServer [as default] (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/@webpack-cli/serve/lib/startDevServer.js:92:24)
child_process.js:679
throw err;
^
Error: Command failed: /home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/.bin/webpack serve --progress --color --port 8081 --hot --inline --config /home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/@mapstore/project/types/standard/config/webpack.config.js
at checkExecSyncError (child_process.js:640:11)
at Object.execSync (child_process.js:676:15)
at Object.<anonymous> (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/@mapstore/project/scripts/start.js:23:6)
at Module._compile (internal/modules/cjs/loader.js:1068:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
at Module.load (internal/modules/cjs/loader.js:933:32)
at Function.Module._load (internal/modules/cjs/loader.js:774:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47 {
status: 2,
signal: null,
output: [ null, null, null ],
pid: 192292,
stdout: null,
stderr: null
}
child_process.js:679
throw err;
^
Error: Command failed: node /home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/@mapstore/project/scripts/start.js --type=standard
at checkExecSyncError (child_process.js:640:11)
at Object.execSync (child_process.js:676:15)
at Object.<anonymous> (/home/offtherailz/work/projects/emsa/emsa-cgd-fe/node_modules/@mapstore/project/bin/mapstore-project.js:28:10)
at Module._compile (internal/modules/cjs/loader.js:1068:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
at Module.load (internal/modules/cjs/loader.js:933:32)
at Function.Module._load (internal/modules/cjs/loader.js:774:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12)
at internal/main/run_main_module.js:17:47 {
status: 1,
signal: null,
output: [ null, null, null ],
pid: 192284,
stdout: null,
stderr: null
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: `mapstore-project start standard`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] 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! /home/offtherailz/.npm/_logs/2021-06-09T15_07_49_729Z-debug.log
Caused by a duplication of webpack instances, solving is not trivial.
The text was updated successfully, but these errors were encountered:
Creating a project and linking MapStore (with
file:<path-to-mapstore>
or withnpm link
) I have the following error running npm start. Customized a little, but I don't think it is the problem.I have this problem on linux.
Caused by a duplication of webpack instances, solving is not trivial.
The text was updated successfully, but these errors were encountered: