fix: remove extra 'use client' directive #261
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
When using Next.js and SWC plugin coverage instrumentation, you will get this error due to the duplication of the use client directive: ``` Error: × The "use client" directive must be placed before other expressions. Move it to the top of the file to resolve this issue. ╭─[/node_modules/.pnpm/vaul@0.9.0_@types+react-dom@18.2.17_@types+react@18.2.43_react-dom@18.2.0_react@18.2.0/node_modules/vaul/dist/index.mjs:1:1] 1 │ "use client" 2 │ "use client";import * as L from "@radix-ui/react-dialog"; ```
|
@Kinbaum is attempting to deploy a commit to the emil Team on Vercel. A member of the Team first needs to authorize it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using Next.js and SWC plugin coverage instrumentation, you will get this error due to the duplication of the use client directive:
Since you've already got this included in the index, there's no need for this config option.
Removing the banner resolves the issue with the plugin.