-
Notifications
You must be signed in to change notification settings - Fork 402
fix(astro): Introduce protect-fallback slot to avoid server islands conflict
#5196
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(astro): Introduce protect-fallback slot to avoid server islands conflict
#5196
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
…tect-component-and-server
🦋 Changeset detectedLatest commit: afd5b79 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
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 |
…tect-component-and-server
…tect-component-and-server
…tect-component-and-server
|
!snapshot |
|
Hey @wobsoriano - the snapshot version command generated the following package versions:
Tip: Use the snippet copy button below to quickly install the required packages. npm i @clerk/agent-toolkit@0.0.4-snapshot.v20250220200839 --save-exact
npm i @clerk/astro@2.3.0-snapshot.v20250220200839 --save-exact
npm i @clerk/backend@1.24.3-snapshot.v20250220200839 --save-exact
npm i @clerk/chrome-extension@2.2.11-snapshot.v20250220200839 --save-exact
npm i @clerk/clerk-js@5.54.0-snapshot.v20250220200839 --save-exact
npm i @clerk/elements@0.23.0-snapshot.v20250220200839 --save-exact
npm i @clerk/clerk-expo@2.8.0-snapshot.v20250220200839 --save-exact
npm i @clerk/expo-passkeys@0.1.22-snapshot.v20250220200839 --save-exact
npm i @clerk/express@1.3.50-snapshot.v20250220200839 --save-exact
npm i @clerk/fastify@2.1.23-snapshot.v20250220200839 --save-exact
npm i @clerk/localizations@3.10.8-snapshot.v20250220200839 --save-exact
npm i @clerk/nextjs@6.12.1-snapshot.v20250220200839 --save-exact
npm i @clerk/nuxt@1.2.1-snapshot.v20250220200839 --save-exact
npm i @clerk/clerk-react@5.24.0-snapshot.v20250220200839 --save-exact
npm i @clerk/react-router@1.1.1-snapshot.v20250220200839 --save-exact
npm i @clerk/remix@4.5.1-snapshot.v20250220200839 --save-exact
npm i @clerk/shared@2.23.0-snapshot.v20250220200839 --save-exact
npm i @clerk/tanstack-start@0.10.1-snapshot.v20250220200839 --save-exact
npm i @clerk/testing@1.4.24-snapshot.v20250220200839 --save-exact
npm i @clerk/themes@2.2.20-snapshot.v20250220200839 --save-exact
npm i @clerk/types@4.47.0-snapshot.v20250220200839 --save-exact
npm i @clerk/ui@0.3.25-snapshot.v20250220200839 --save-exact
npm i @clerk/vue@1.3.0-snapshot.v20250220200839 --save-exact |
Description
We have a naming conflict between our Astro SDK
<Protect >component and the Astro server islands fallback content slot.The
fallbackslot from our<Protect >component is intended to render content when a user is unauthorized while thefallbackslot for server islands is used to show a loading content for example.To resolve this, we've introduced a new
protect-fallbackslot while maintaining backwards compatibility with the originalfallbackslot.Example:
Resolves ECO-419
Checklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change