-
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): Revert "Use use client
directive to support sha…
#1806
Conversation
🦋 Changeset detectedLatest commit: cecf74d 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 |
!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/chrome-extension
npm i @clerk/[email protected] # @clerk/clerk-js
npm i @clerk/[email protected] # @clerk/clerk-expo
npm i @clerk/[email protected] # gatsby-plugin-clerk
npm i [email protected] # @clerk/nextjs
npm i @clerk/[email protected] # @clerk/clerk-react
npm i @clerk/[email protected] # @clerk/remix
npm i @clerk/[email protected] |
e37df91
to
01bb8ca
Compare
This reverts commit 00d9d42 Revert "chore(backend): Warn about apiKey deprecation" This reverts commit 1a2f12b Revert "chore(backend): Warn about httpOptions deprecation" This reverts commit 838475b. Revert "chore(backend): Warn about InterstitialAPI deprecation" This reverts commit 51a5c39. Revert "chore(backend): Warn about picture/logoUrl/profileImageUrl (image related) deprecations" This reverts commit 077ce3a Revert "chore(backend): Warn about pkgVersion deprecation" This reverts commit 362caaa. Revert "chore(backend): Warn about clockSkewInSeconds deprecation" This reverts commit f500d46. Revert "chore(backend): Warn about backend api return format deprecation" This reverts commit c937990. Revert "chore(backend): Warn about __unstable_options deprecation" This reverts commit 54ba397.
!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/chrome-extension
npm i @clerk/[email protected] # @clerk/clerk-js
npm i @clerk/[email protected] # @clerk/clerk-expo
npm i @clerk/[email protected] # gatsby-plugin-clerk
npm i [email protected] # @clerk/nextjs
npm i @clerk/[email protected] # @clerk/clerk-react
npm i @clerk/[email protected] # @clerk/remix
npm i @clerk/[email protected] |
!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/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] |
@nikosdouvlis I'm still seeing this error using
and here is my 'use server';
import { db } from '@/lib/db';
import type { RecipeCreate } from '@/types';
import { auth } from '@clerk/nextjs';
import { redirect } from 'next/navigation';
export async function createRecipe(recipe: Omit<RecipeCreate, 'userId'>) {
const { userId } = auth();
if (!userId) {
throw new Error('You must be signed in to create a new recipe');
}
const newRecipe = await db.recipe.create({ data: { ...recipe, userId } });
redirect(`/recipes/${newRecipe.id}`);
} |
@OwenVey Thank you for reporting this one, forwarding this to the team ASAP |
@OwenVey, if you import the Server Action into a Server Component and then pass it as a prop to the Client Component does that resolve the issue? |
@royanger yeah, I was the one who posted it on Discord. I think it's definitely a Next.js issue |
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. |
Temporarily resolve
Description
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