Sourcemaps seem to break when replacing "ngInject" prologues.
See original GitHub issueI noticed if I use this loader to replace the “ngInject”; prologues my source maps no longer open the original file.
{
loader: 'string-replace-loader',
options: {
multiple: [
{
search: /["']ngInject["'];*/,
replace: '',
flags: 'g'
}
]
}
},
{
loader: 'ng-annotate-loader'
},
{
loader: 'babel-loader',
options: {
cacheDirectory: true
}
},
Perhaps I’m missing something? If I take out the string-replace-loader source maps are okay again.
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Can't find javascript source map to debug in chrome devtools
However, I can't seem to actually find the source map so that I can place a break point. I can't find it in...
Read more >Overview - TypeScript
TypeScript 3.4 can now produce generic function types when inference from other generic functions produces free type variables for inferences. This means many ......
Read more >Software self-defense systems and methods - Google Patents
The signature of a program can also be changed by replacing instructions and/or ... the source map will often appear quite random; by...
Read more >d3n8a8pro7vhmx.cloudfront.net/themes/5654d01801925...
//This can still fail, but catches the most reasonable //uses of .. break; ... utils":32,"source-map":38}],10:[function(require,module,exports){ ...
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
@snipking I basically have the same setup like you. I hope my PR will fix this: https://github.com/Va1/string-replace-loader/pull/28.
Same to me.