Generating source maps and using TerserPlugin #19794
Unanswered
triangletrianglesquareplusx
asked this question in
Q&A
Replies: 1 comment 3 replies
-
|
Don't touch |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello. I am trying to use webpack (5.6.0) with TerserPlugin and I want to generate source maps.
My webpack config has dev-tools: sourcemap already but as far as I have read this only means that for example, Chrome can read them, IF they exist.
My TerserPlugin config looks like this:
Is this the proper way to do it? I am running into an issue that I would like to debug but still I am seeing files like:
app_806d6ee3ef63ac7daa.....14 and I am trying to understand what is happening.
Some llm questioning has lead me to an example which says:
and the llm is 'stating' that we should have sourceMap set on the plugin ITSELF not in the terserOptions.
For example this dude:
#19264
Does exactly that for his sourceMap:true
Beta Was this translation helpful? Give feedback.
All reactions