-
Notifications
You must be signed in to change notification settings - Fork 12
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
Breaking with next.js 13 app folder #183
Comments
Looks like plugin affects something, probably not a bug in next.js upstream. |
Looks like there's common symptom when custom transform / plugin is enabled: vercel/next.js#41994 |
@gaetleba where you somehow able to fix this issue with the experimental app feature? |
No, I'm using babel for now |
I've been peeking this bit, this is mostly due to server component side transform error. I can't explain why it occurs with this specific plugin, as well as cannot change plugin's behavior to amend it (since I don't have explanation why server component is being affected). I'm going to close this for now. If anyone have minimal reproduction which doesn't have server component involved and transforming with this plugin creates offending codes, I may able to look into. |
Hi, I'm not sure if this is a problem with the plugin or Next but here is a bug I'm encountering :
Trying to use this plugin with a Next.js project and the latest next feature app folder I get the following bug:
Using the same project with babel and
babel-plugin-istanbul
works fine.Here is a reproduction project : https://github.com/gaetleba/swc-plugin-coverage-instrument-bug-reproduction
I made a report over there too: vercel/next.js#42580
The text was updated successfully, but these errors were encountered: