Open richtera opened 4 years ago
Same problems for inline
, I will look solution in near future
Very strange, reproduced on Chrome, but works fine in Firefox
Let's wait answer from chromium teams
@evilebottnawi, shouldn't the devtoolNamespace be different for the new entry, to prevent collusion for browsers that keep a single source map for all threads (like chrome) ?
@alexander-akait any updates on this issue? (or a workaround?)
@edenhermelin What is webpack version?
@edenhermelin What is webpack version?
@alexander-akait these are the versions:
"webpack": "4.46.0",
"webpack-cli": "4.6.0",
Still not fixed by chrome https://bugs.chromium.org/p/chromium/issues/detail?id=1111297, you can try to look at this in Firefox, should work
Moved to Hotlist
(Hotlist-DevTools-SourceMaps
), so should be fixed in near future (hope)
@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
const worket = new Worker(new URL('./worker.js', import.meta.url));
@edenhermelin Maybe make sense to migrate on webpack v5 and avoid using this loader due
const worket = new Worker(new URL('./worker.js', import.meta.url));
Migration is quite tricky as the vue-electron-builder plugin doesn't support it yet. I opened another issue for the chromium team, hope it'll help too.
Is there an option to disable source maps for worker-loader?
@AprilArcus Please migrate from worker-loader
if you use webpack
v5
Impossible at this time due to https://github.com/webpack/webpack/issues/13801
Expected Behavior
When pointing to the source code of the webworker in webpack it should show the source of the worker and not the loader. My webworker....
This is what should show so I could step through the code.
Actual Behavior
What's shown when browsing to it in webpack://
Code
How Do We Reproduce?
According to this debugging any webworker with the same versions should show this problem. I have previously used worker-loader in another version of webpack/node/npm and did not have this problem. I am suspecting it's webpack or a new version of worker-loader that's somehow mixing the source code of the loader and the actual worker when outputting it to the map files. But it could also be a webpack issue only allowing a single map to be output. Not sure, but currently I'd have to turn off mapfiles during debugging.