-
Notifications
You must be signed in to change notification settings - Fork 282
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
fix(nextjs, shared): Restores reverted commits and fixes issue with shared in nextjs #1807
Conversation
🦋 Changeset detectedLatest commit: 319d166 The changes in this PR will be included in the next version bump. This PR includes changesets to release 11 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
635ad37
to
488bc28
Compare
Since we've seen issues with this PR I think this round we should be more conservative and test more extensively. Basically, we'll need to check our usages of We probably should do two things for sure:
|
b71123b
to
07c73ae
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it make sense to group all client related stuff with a "client-boundary" folder/file like we do for nextjs ?
f484783
to
0305080
Compare
82278e5
to
3613794
Compare
c019805
to
e59325c
Compare
0b7ecb7
to
c01b89f
Compare
@panteliselef Let's open a discussion in team-js channel and see how it goes. I think it makes sense. |
c01b89f
to
bffe9d9
Compare
!snapshot |
Hey @nikosdouvlis - the snapshot version command generated the following package versions:
Tip: use the snippet copy button below to quickly install the required packages. # @clerk/backend
npm i @clerk/[email protected] # @clerk/chrome-extension
npm i @clerk/[email protected] # @clerk/clerk-js
npm i @clerk/[email protected] # @clerk/clerk-expo
npm i @clerk/[email protected] # @clerk/fastify
npm i @clerk/[email protected] # gatsby-plugin-clerk
npm i [email protected] # @clerk/localizations
npm i @clerk/[email protected] # @clerk/nextjs
npm i @clerk/[email protected] # @clerk/clerk-react
npm i @clerk/[email protected] # @clerk/remix
npm i @clerk/[email protected] # @clerk/clerk-sdk-node
npm i @clerk/[email protected] # @clerk/shared
npm i @clerk/[email protected] # @clerk/themes
npm i @clerk/[email protected] # @clerk/types
npm i @clerk/[email protected] |
bffe9d9
to
63f77bd
Compare
This reverts commit aae1150.
63f77bd
to
25e6acd
Compare
…red imports"" This reverts commit 01bb8ca.
…d drop unused"" This reverts commit 0df7e2c.
…ackage"" This reverts commit 9626959.
…/nextjs) node_modules/@clerk/shared/dist/cjs/hooks/createContextAndHook.js (43:35) @ createContext createContext only works in Client Components. Add the "use client" directive at the top of the file to use it. Read more: https://nextjs.org/docs/messages/context-in-server-component at createContextAndHook (webpack-internal:///(rsc)/./node_modules/ @clerk/shared/dist/cjs/hooks/createContextAndHook.js:48:38) at eval (webpack-internal:///(rsc)/./node_modules/@clerk/shared/ dist/cjs/hooks/contexts.js:53:110)
Even though we had imports of `@clerk/shared` the dependency was missing from package.json of `@clerk/nextjs` and the `@clerk/shared` defined in `@clerk/clerk-react` package.json was used (that's why no error was raised from the imports).
…ache issue: Error: Failed to execute turbo (Unable to locate Go binary). ERROR Unable to find Go binary. Please report this issue at ... turbo GH: vercel/turborepo#5381
9acaa62
to
319d166
Compare
This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Description
Review it per commit
After restoring the reverted commits of #1806 , i found that the error was raised because there was some CSR only rendering files in
@clerk/shared
that did not have theuse client
directory set.The culprits were:
packages/shared/src/hooks/contexts.tsx
packages/shared/src/hooks/createContextAndHook.ts
I tested the fix in the local
playground/app-router
and it seems that there is no error thrown.Checklist
npm test
runs as expected.npm run build
runs as expected.Type of change
Packages affected
@clerk/clerk-js
@clerk/clerk-react
@clerk/nextjs
@clerk/remix
@clerk/types
@clerk/themes
@clerk/localizations
@clerk/clerk-expo
@clerk/backend
@clerk/clerk-sdk-node
@clerk/shared
@clerk/fastify
@clerk/chrome-extension
gatsby-plugin-clerk
build/tooling/chore