-
Notifications
You must be signed in to change notification settings - Fork 16
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
Crash when using with Next.js config #6
Comments
same error here on |
comment ['@swc-jotai/react-refresh', {}], is works for me |
Same on next: 13.2.4-canary.2 |
Looking into it :) |
Try latest version of the plugins please! Reopen if the issue remains. |
Thanks for looking into it @Thisen. Looks like the issue changed into something else:
I can't reopen. |
Can you try latest Next.js If that doesn't work, please provide a reproduction. |
@Thisen Thanks for working on this. I got the same issue. |
Got the same problem. Next 13.2.4 |
An update: |
I believe we're experiencing these issues: |
I have the exact 2 issues, still can't use the plugins at the moment. Looking forward to the update! |
Same issue issue. Looking forward to the fix! |
Issue still persists with next 13.3.0 and debug-label 0.0.9 and react-refresh 0.0.7 |
Looks like it's still a reported issue: |
Also having this problem. The Nextjs issue just got patched however, so we just need to update the plugin and all's good. |
Same issue here next@13.3.0 |
@Thisen - New error after updated |
Same issue for next@13.3.0 |
Updating swc_core to 0.75.23 and Next.js to 13.3.1 has fixed it for my own plugin that was having a similar issue |
same error here on nextjs 13.3.1 |
This should be fixed in latest versions hopefully! |
Updating to Next 13.3.1 & @swc-jotai/react-refresh v0.0.8 is giving me a new error:
As far as I can tell, @swc-jotai/debug-label v0.0.10 does not throw any errors. |
Still happens to me using Next.js v13.4.1, tried pretty much everything. I'm seeing following error in the console output: .thread '<unnamed>' panicked at 'assertion failed: prev.start > max', /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wasmer-compiler-3.2.1/src/engine/trap/frame_info.rs:224:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }', /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wasmer-compiler-3.2.1/src/engine/trap/frame_info.rs:220:39 Would really appreciate if you could take a look at this. Thank you for the effort. |
I created a new issue because this one was closed. Please add a comment here - #13 |
module.exports = {
experimental: {
swcPlugins: [['@swc-jotai/react-refresh', {}]],
},
} The issue still exists in version |
I can confirm the same issue on next@13.4.19 and @swc-jotai/react-refresh@0.1.0. @Thisen could we reopen this please? |
@Thisen can confirm the same for |
My Next.js crashed when I add this config to
next.config.js
:Console logs:
I notice there is
Users/thisen
value mentioned but this user is not on my machine, maybe some hard-coded issue?The text was updated successfully, but these errors were encountered: