[Bug]: Invalid sources in WebPack-generated map file

[fpascutti]

💻

• Would you like to work on a fix?

How are you using Babel?

babel-loader (webpack)

Input code

Small project where issue can be reproduced can be found here:
https://github.com/fpascutti/babel-7.17.3-sourcemaps-issue

Configuration file name

No response

Configuration

No response

Current and expected behavior

With @babel/core >= 7.17.3, the source map file generated by Webpack contains Javascript code instead of the expected Typescript code.
Using @babel/core 7.17.2, the source map file generated by Webpack properly contains the original Typescript code.

Environment

System:
OS: Windows 10 10.0.19042
Binaries:
Node: 16.13.1 - C:\nodejs\node.EXE
npm: 8.1.2 - C:\nodejs\npm.CMD
npmPackages:
@babel/core: ^7.17.3 => 7.17.4
@babel/preset-env: ^7.16.11 => 7.16.11
babel-loader: ^8.2.3 => 8.2.3
webpack: ^5.69.0 => 5.69.0

Possible solution

Workaround is to force @babel/core to version 7.17.2.

Additional context

No response

[babel-bot]

Hey @fpascutti! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite.

[nicolo-ribaudo]

cc @jridgewell

[alan-agius4]

In the Angular CLI we are also experiencing a similar issue. It seems that it only effects non posix OS.

[jridgewell]

Hi all, I believe I have a fix in #14282, but I don't have a Windows machine to fully test it. Can any of you apply the patch and see if it fixes the merging?

[jridgewell]

Scratch that, I was able to verify the fix using GH Actions. Thanks so much for the reproduction @fpascutti!