-
-
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
failed to read input source map - @swc/jest + yarn PnP workspaces #9416
Comments
Sigh. Closing because only after raising this issue I spot the error in my regex. However, hopefully someone else may see this issue and realise their regex is broken too. |
Re-opening as I've finally managed to get a minimal repro of the original issue I was facing relating to importing code from workspace packages with peer dependencies. |
I've been seeing this issue since v1.4.12 :-( |
I see that #9422 suggests it may help with #8910, which is a duplicate of this issue (without a reproduction). I've tried 1.7.11, but I'm still getting the same error message, with no additional details:
|
It still seems to be using |
I can confirm that said file does exist (in |
I am facing the same issue but with Here's a reproduction:
|
Can you update |
I have updated @swc/core to v1.7.18 but issue still persists |
Same issue with pnpm workspaces , source maps are present. |
Now, I have more information in the latest release of swc. For me, the error is actually coming from one of the dependencies that doesn't have the source map in the package.
|
with docker + pnpm workspace and
an error
Plus in my case I can already have compiled js files and swc adds
|
Describe the bug
Using yarn PnP with workspaces causes swc to emit
Switching to the node-modules linker, stops the errors.
I'd been seeing this for a while, and hoped that #8789 might fix it, but it appears not to
Input code
Config
Playground link (or link to the minimal reproduction)
https://github.com/mrginglymus/swc-repro
SWC Info output
Expected behavior
No errors :)
Version
1.7.9
Additional context
This only happens when importing code from a workspace package with peer dependencies.
The text was updated successfully, but these errors were encountered: