Furkan Erdem

I had a chance to work a bit on this issue. I'm able to get the original lines and locations of the error using the source map as @alexander-akait advised....

I've been working on this problem since last week trying to find possible solutions. I'm still familiarizing myself with the codebase so I'm definitely open for feedback. Just to ensure...

In order to confine the fix to errored modules only as @alexander-akait suggested, I deferred updating the error location to the module factorization.

@Threebow [TsconfigPathsPlugin](https://github.com/dividab/tsconfig-paths-webpack-plugin/tree/master) does exactly what you're trying to do, you can check it out.

> Why closed? 😞 I was planning to add `updateErrorLocation` function to webpack-sources repo and then open this again after it got merged. Should I keep it open?

@jssuttles I guess so, no PR's referencing this issue has been merged.

I've been tinkering with this issue and it seems like CSS plugin skips preprocessing steps if the transformer is lightningCSS(1), thus it can't benefit from the `additionalData` option. `additionalData` might...

Seems like `template` nodes' children are not inserted into `node.childNodes` but `node.content.childNodes`. As the html parser only traverses `node.childNodes` (1) template children are skipped. I don't know if this behaviour...