-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
transform providing an inputSourceMap throws an error [bad reference to source #299] #8789
Comments
@kdy1 Is it fixed in v1.4.12? I tried to use 1.4.12 and the problem still exists. https://stackblitz.com/~/github.com/noyobo/swc-issues
|
Seeing the same when updating from
|
My hunch is that this issue is caused by npm packages that include references to source maps (via One example is |
@davidmurdoch #8951 should fix your issue, although I'm not sure if it fixes this issue |
**Description:** Some libraries generate source maps but do not upload them to npm, which causes SWC to fail. **Related issue:** - #8789 (comment)
Sorry, I can't provide a smaller reproducible example yet, I don't know what boundary conditions are triggered. |
As an FYI - All of the errors we were seeing as a result of missing sourcemaps are not appearing. The sourcemaps are still not there, but we are at least not seeing those specific errors. Thank you @kdy1! |
Describe the bug
https://stackblitz.com/~/github.com/noyobo/swc-issues
Input code
No response
Config
Playground link (or link to the minimal reproduction)
https://stackblitz.com/~/github.com/noyobo/swc-issues
SWC Info output
No response
Expected behavior
The transformed sourceMap content can be used again
Actual behavior
No response
Version
1.4.11
Additional context
No response
The text was updated successfully, but these errors were encountered: