-
-
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
[BUG] - Error: It's currently unsupported to use "export *" in a client boundary. #2749
Comments
I had the same problem, so I went back to a previous version, but weirdly the problem persists. I went back to:
but the problem persists. I deleted node_modules and .next for a clean install but the problem persists, does anyone know how to fix this? |
See this comment |
@wingkwong - the solution is a BREAKING change. This should not be happening in a minor version update. |
@paveldpetrov we added the |
I still get this issue with version 2.3.2 |
@Armandotrsg could you create a stackblitz project? |
I also got this error in my Next.js project |
@work7z are using the latest version? We recently released some bug fixes. If so, could you create a stackblitz project? |
@wingkwong In version 2.3.3,Next.js Failed to compile:
|
@jrgarciadev - Hi! The error is not fixed. Here's codesandbox with the latest version. |
yes, I've tired to compile with latest version and old version, they're both failed later I would provide a sandbox for it |
I did the same thing what the last time. Exported manually all items form packages and works. `"use client"; // src/index.ts |
I am also experiencing this bug as well, just after updating my JSON package. React NextUI is the culprit here I guess |
I removed @nextui-org/react and replaced it with all subpackages,
it works fine now! |
@ldystudio this workaround is a breaking change and it is not ok. |
Sort of fixed mine, but the Dropdown Trigger menu is not working |
https://nextui.org/docs/components/dropdown The dropdown menu on the webpage is not working, I guess the developer team must be aware of this |
After updating from @nextui-org/react: |
Upgraded to latest version (2.3.4), got the same issue. I'll wait for this issue to be resolved before upgrading again. |
hi bro, here's a workaround for you if you still want to use old version without adjusting existing code (like change import statement and add 'use client') first step:set your version as "x.x.x", remember there's no '^' or '~' prefix otherwise this dependency will still install latest package which contains BREAKING CHANGE. "@nextui-org/react": "2.2.9", second step:shutdown related services, remove folders third step:re-install node_modules |
I'm afraid that I couldn't adjust these import statement and add 'use client' one by one since there're innumerable source code files... that's a viable workaround for my project, btw, I'm uncertain why NextUI has to provide this breaking change... it should be avoided in minor version releases like others just mentioned |
@paveldpetrov I noticed some issues with your codesandbox, you need to add the e.g. v2.2.9 - With the issue v2.2.9 - Fixed v2.3.4 - Same code as v2.2.9 working without any change References: |
This works indeed. Fixed it with this workaround in my code |
Guys can some of you confirm if this issue is fixed using this version?
|
I can confirm the problem with version 2.3.4. Rolling back to 2.2.9 solved it. |
@MaxBalaban please try with this version |
I just tried this version, and it's working well with no issues. It was a new deployment without cache (via Vercel). |
Nice thank you! @MaxBalaban |
I just tried version |
Fix available in v2.3.5 https://github.com/nextui-org/nextui/releases/tag/%40nextui-org%2Freact%402.3.5 |
Back on track! |
NextUI Version
2.3.1
Describe the bug
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Clean installation
Expected behavior
I deleted the use client from the file ./node_modules/@nextui-org/react-utils/dist/index.mjs and everything worked
Screenshots or Videos
No response
Operating System Version
macOS
Browser
Chrome
The text was updated successfully, but these errors were encountered: