nextui: [BUG] - Error: It's currently unsupported to use "export *" in a client boundary.

NextUI Version

2.3.1

Describe the bug

err: Failed to compile.
err: ./node_modules/@nextui-org/react-utils/dist/index.mjs
err: Error: It's currently unsupported to use "export *" in a client boundary. Please use named exports instead.

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

About this issue

Original URL
State: closed
Created 2 months ago
Reactions: 7
Comments: 32 (9 by maintainers)

Most upvoted comments

@wingkwong - the solution is a BREAKING change. This should not be happening in a minor version update.

paveldpetrov on Apr 17, 2024

Fix available in v2.3.5 https://github.com/nextui-org/nextui/releases/tag/%40nextui-org%2Freact%402.3.5

jrgarciadev on Apr 18, 2024

I removed @nextui-org/react and replaced it with all subpackages, e.g.

import { Button } from "@nextui-org/button"
import { Code } from "@nextui-org/code"

it works fine now!

ldystudio on Apr 18, 2024

I still get this issue with version 2.3.2

Armandotrsg on Apr 18, 2024

I just tried version @nextui-org/react": "0.0.0-dev-v2-20240418192457 and it works as expected. @jrgarciadev

ivstudio on Apr 18, 2024

Guys can some of you confirm if this issue is fixed using this version?

"@nextui-org/react": "0.0.0-dev-v2-20240418192457"

@paveldpetrov ?

@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

jrgarciadev on Apr 18, 2024

Guys can some of you confirm if this issue is fixed using this version? "@nextui-org/react": "0.0.0-dev-v2-20240418192457" @paveldpetrov ?

@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).

MaxBalaban on Apr 18, 2024

Guys can some of you confirm if this issue is fixed using this version?

"@nextui-org/react": "0.0.0-dev-v2-20240418192457"

@paveldpetrov ?

@MaxBalaban please try with this version

jrgarciadev on Apr 18, 2024

@jrgarciadev @ivstudio

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 node_modules, .cache, .next if have

third step:

re-install node_modules

work7z on Apr 18, 2024

@jrgarciadev - Hi! The error is not fixed. Here’s codesandbox with the latest version.

paveldpetrov on Apr 18, 2024