edenhermelin

@alexander-akait any updates on this issue? (or a workaround?)

> @edenhermelin What is webpack version? @alexander-akait these are the versions: ``` "webpack": "4.46.0", "webpack-cli": "4.6.0", ```

@alexander-akait thanks for the quick reply! unfortunately Im using Electron so it's not possible for me to try that in electron 😞

> @edenhermelin Maybe make sense to migrate on webpack v5 and avoid using this loader due > ```js > const worket = new Worker(new URL('./worker.js', import.meta.url)); > ``` Migration is...

@bryan-gilbert there is a bug with Electron over paralls VM that may cause the issue you are facing. Try to disable hardware acceleration on your electron main file

sure, basically in the index file you should add the following: ``` app.disableHardwareAcceleration(); ``` also, in here you can find some more relevant information: https://github.com/electron/electron/issues/22119

Seems like it happens when the library is imported inside a web worker (Bundled with webpack). Any ideas?

@MattLish did something related to the issue changed in versions greater than `8.2` ?

@sindresorhus thanks for the update! unfortunately, it seems as `conf` -> `ajv` still generates these warnings. 😞 ``` DevTools failed to load SourceMap: Could not load content for http://localhost:8080/Users/myUser/projects/my_test_repo/node_modules/conf/node_modules/ajv/dist/ajv.js.map: HTTP...

@segevfiner thank you so much for this, it helps us a lot! @egoist - looks like the CI build fails for linter (on the dynamic import). Any chance you can...