I'm writing a webpack-react-typescript kit, and I've found that the source-map
can't direct to the source code.
It directs to the webpack-internal://src/App.tsx file
, this file has some webpack injection code.
Another computer has both the webpack://
and webpack-internal
domain, and the source map, which in the webpack://
domain can't direct to the current source code.
So what I want to know is:
webpack
and webpack-internal
?webpack://
and the other one doesn't?Webpack is a free and open-source module bundler for JavaScript. It is made primarily for JavaScript, but it can transform front-end assets such as HTML, CSS, and images if the corresponding loaders are included. Webpack takes modules with dependencies and generates static assets representing those modules.
Webpack is a popular module bundling system built on top of Node. js. It can handle not only combination and minification of JavaScript and CSS files, but also other assets such as image files (spriting) through the use of plugins.
Compared to Webpack 5 with lazy compilation, Vite has a slightly slower dev startup time and somewhat longer production build time even with code-splitting enabled. But one of the big reasons developers love Vite is the near-instant feedback loop between saving a file and seeing your changes in the browser.
There's an error in chrome displaying source maps, which is the reason why it is suffixed like that.
https://github.com/webpack/webpack/blob/8a7597aa6eb2eef66a8f9db3a0c49bcb96022a94/lib/EvalSourceMapDevToolModuleTemplatePlugin.js#L88-L95
The chrome team seems to be neutral to solving this https://twitter.com/ChromeDevTools/status/960972070711476224
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With