R
R
Ruslan Absalyamov2019-12-31 14:15:00
Google Chrome
Ruslan Absalyamov, 2019-12-31 14:15:00

Why is my source map not generated when I change it?

I have such a moment that when for the first time I compiled the file through webpack, then chrome in the debugger normally shows files from the source map. If I change something in the code and then compiled it, then the previous code remains in the debugger in chrome, but it processes it as a new compiled code. I'm using node 11.6.0 if that matters. To make it clear what I mean, I will make a special mistake. At first we compile for the first time
5c2b2074d49ab089737425.png
And in the debugger everything is also normal
5c2b207a68441721746823.png
Now I make some mistake
5c2b212e5756c164815202.png
That is, there is no key variable at all, then when compiling the file, we try to open it in the browser and see such an interesting thing
5c2b22d56bb8f819660423.png
. What could be the problem?

Answer the question

In order to leave comments, you need to log in

1 answer(s)
R
Ruslan Absalyamov, 2019-01-01
@rusline18

The problem was in chrome and not webpack, in network I checked the disabled cach flag and everything worked fine and you can debug normally

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question