Webpack build error with 0.18
See original GitHub issuemonaco-editor version: 0.18.0
Steps or JS usage snippet reproducing the issue:
I am trying to build the latest monaco with webpack but I am getting the following error:
./node_modules/monaco-editor/esm/vs/base/worker/defaultWorkerFactory.js 35:32-39
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
You can reproduce this error by cloning https://github.com/vega/editor/tree/dom/upgrade and running
yarn && yarn start
Issue Analytics
- State:
- Created 4 years ago
- Reactions:13
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Webpack build error - node.js - Stack Overflow
Strange workaround: I zipped my entire node_modules map and transfered it to PC_A and placed it correctly. Now webpack builds just fine. So...
Read more >PSA: Old Elm binary downloads now gone - Show and Tell
This will download binaries from githhub. Unfortunately, this will not work if you are also using the elm-webpack-loader as the 0.18-compatible ...
Read more >monaco-editor-webpack-plugin - npm
A webpack plugin for the Monaco Editor. Latest version: 7.0.1, last published: a year ago. Start using monaco-editor-webpack-plugin in your ...
Read more >Development - webpack 3 documentation
When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location. For example, if...
Read more >Webpack Error using latest version 3.6.0 (Example) - Treehouse
Hi,. when running npm run build webpack is transpiling with no error. But in Chrome developer tools I get the following error: "Uncaught ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Fixed via https://github.com/microsoft/vscode/commit/1ce58ccde7941cccd5448cb95f81e2f469db35d1
Not sure if it is related but in addition to that warning I’m also getting the following error: