Sourcemaps always generated inline
See original GitHub issueWebpack 3.1.1 ts-loader 3.5.0
I want the sourcemaps to be generated separately in my dist folder, not inline. Inline is bad, because when I want to to check my bundle.js under sources tab the browse starts to hang, because the file is too big I guess.
I tried different devtool
settings but the result is always the same, sourcemaps are generated inline
!
webpack.config.js devtool:“nosources-source-map”,
ts.config.json
{
“compilerOptions”: {
“module”: “esnext”,
“target”: “es5”,
“diagnostics”: true,
“sourceMap”: false, // can also change it to true same result
“moduleResolution”: “node”,
“noEmitOnError”: true,
“lib”: [
“dom”,
“es5”,
“scripthost”,
“es2015.promise”
]
},
“include”: [
“./src/**/*”
]
}
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Source maps are always generated inline · Issue #132 - GitHub
But my files always have inline source maps in them. I checked and the babel documentation and they say the parameter should be...
Read more >Why inline source maps? - Stack Overflow
The rational for inlining the source maps with your minified files is that the browser is parsing the exact same JavaScript in development...
Read more >4 Reasons Why Your Source Maps are Broken - Sentry Blog
It's possible to inline your entire original source code into the source map itself. Inside the source map, this is referred to as ......
Read more >Should I Use Source Maps in Production? | CSS-Tricks
Typically, source maps are a configuration option from the preprocessor. Here's Babel's options.
Read more >What Are Source Maps and How to Properly Use Them
Inline source maps are simply data URLs that contain the JSON object we saw earlier encoded in base64. It will look something like...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yup. Been there!
Yeah, the issue was behind the screen after a very long day… 😉
But thinking about this, perhaps there should be a warning message, when command line arguments override configuration settings in webpack, … well this has nothing to do with TS.