chore(clerk-js,ui): upgrade to Rspack 2

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm

[jacekradko]

Upgrades @clerk/clerk-js and @clerk/ui bundling from Rspack 1.7.x to Rspack 2 (2.0.6). Every variant builds (7 for clerk-js, 3 for ui), and the unit + integration matrix and bundlewatch are all green. Node minimum moves to 22.12.0, a Rspack 2 requirement.

The part worth real scrutiny is the config migration in packages/clerk-js/rspack.config.mjs and packages/ui/rspack.config.js: the config moves to ESM (Rspack 2 core is pure ESM), output.libraryTarget: 'x' is rewritten to output.library: { type: 'x' } across both configs, and experiments.cache graduates to a top-level cache. Since clerk-js/ui load into apps pinned on older SDK versions, the thing to confirm is that the per-variant bundle shape (library type, chunking) is unchanged.

Two small riders come along: bundlewatch budgets nudged up for Rspack 2's marginally larger gzip (clerk.browser.js 70→72KB, base-account-sdk 203→205KB, otherwise within ~0.1KB), and two @clerk/shared typecheck fixes, dropping the now-built-in NoInfer import from @tanstack/query-core and guarding script.nonce in loadScript.ts (matching #8177).

Holding the merge while the TS 6.0 work (#8177) settles, since the two overlap in the bundlewatch config and @clerk/ui's build.

Summary by CodeRabbit

• Chores
  • Upgraded build infrastructure to Rspack 2 with optimized bundle handling
  • Updated minimum Node.js version requirement to 22.12.0
  • Adjusted bundle size to 72KB

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clerk-js-sandbox	Ready	Preview, Comment	Jun 12, 2026 12:05pm
swingset	Ready	Preview, Comment	Jun 12, 2026 12:05pm

[changeset-bot]

🦋 Changeset detected

Latest commit: c31eb18

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@clerk/clerk-js	Patch
@clerk/ui	Patch
@clerk/chrome-extension	Patch
@clerk/expo	Patch
@clerk/swingset	Patch

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

[pkg-pr-new]

Open in StackBlitz

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@8382

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@8382

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@8382

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@8382

@clerk/expo

npm i https://pkg.pr.new/@clerk/expo@8382

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@8382

@clerk/express

npm i https://pkg.pr.new/@clerk/express@8382

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@8382

@clerk/hono

npm i https://pkg.pr.new/@clerk/hono@8382

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@8382

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@8382

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@8382

@clerk/react

npm i https://pkg.pr.new/@clerk/react@8382

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@8382

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@8382

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@8382

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@8382

@clerk/ui

npm i https://pkg.pr.new/@clerk/ui@8382

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@8382

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@8382

commit: c31eb18

[coderabbitai]

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

• @coderabbitai resume to resume automatic reviews.
• @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

• ▶️ Resume reviews
• 🔍 Trigger review

📝 Walkthrough

Walkthrough

This PR upgrades Rspack to version 2 across the workspace and migrates the clerk-js build configuration from CommonJS to ESM. The core change replaces deprecated libraryTarget API with the modern library.type format, consolidates cache configuration, and updates all related npm scripts and workspace dependencies.

Changes

Rspack 2.0 Upgrade and Configuration Updates

Layer / File(s)	Summary
ESM imports, module interop, and config export packages/clerk-js/rspack.config.mjs	Replace CommonJS requires with ESM imports, add createRequire and __dirname compatibility shims from import.meta.url, import package.json as JSON module, and switch config export from module.exports to export default.
Output library API migration packages/clerk-js/rspack.config.mjs	Replace deprecated output.libraryTarget with output.library: { type: ... } across all bundle variants (UMD production, ESM/CJS variants, and dev builds).
Development cache consolidation packages/clerk-js/rspack.config.mjs	Simplify dev caching by removing cache: true plus experiments.cache.type and replacing with cache: { type: 'memory' }.
Package scripts and devDependencies packages/clerk-js/package.json	Update clerk-js npm scripts to reference rspack.config.mjs, remove --analyze CLI flag from build:analyze, upgrade @rsdoctor/rspack-plugin to ^1.5.9, and add @rspack/dev-server.
Workspace catalogs, bundle threshold, and type imports pnpm-workspace.yaml, packages/clerk-js/bundlewatch.config.json, packages/shared/src/react/query/useQuery.ts	Update pnpm rspack catalog versions to 2.0.x range, extend trustPolicyExclude with tinyclip, increase clerk-js bundlewatch maxSize threshold, and remove NoInfer from @tanstack/query-core import.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Suggested reviewers

• dstaley
• wobsoriano

Poem

🐰 With Rspack 2.0 and files in ESM flow,
The bundle output now gleams in runtime glow,
Libraries restructured from target to type so clean,
Cache consolidated—the smoothest build scene!
TypeScript imports refined, thresholds adjusted right,
Modernization complete, the config shines bright! 🚀

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'chore(clerk-js,ui): upgrade to Rspack 2' accurately and specifically summarizes the main change—upgrading Rspack to version 2 for the clerk-js and ui packages.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 2

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/rspack.config.mjs (1)

2-518: ⚠️ Potential issue | 🟠 Major

Merge blocker: no test coverage/verification for a build-system migration

This PR changes core bundling behavior (Rspack major version, config format, output library config, cache semantics) but includes no added/updated tests or automated verification in the change set. Please add and run migration-focused build/test coverage (at least smoke coverage across the declared variants) before merge.

As per coding guidelines, "If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes."

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.
In `@packages/clerk-js/rspack.config.mjs` around lines 2 - 518, The PR introduces
a major rspack-based bundling change but lacks migration/verification tests; add
automated smoke tests that build and validate each declared variant (use
variants object keys and entryForVariant, prodConfig and devConfig outputs) to
CI: create test scripts that invoke the rspack build for clerkBrowser,
clerkLegacyBrowser, clerkNative, clerk (ESM/CJS) and clerkNoRHC variants, assert
successful exit and presence of expected output files (check
output.filename/library type for commonjs/module/umd and chunking behavior), and
add these tests to the repository CI pipeline so they run on PRs before merge.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.
Inline comments:
In @.changeset/rspack-2-upgrade.md:
- Line 6: Add a CI-backed smoke test that verifies the Rspack 2 build/runtime
produces working bundles for the changed packages (`@clerk/clerk-js` and
`@clerk/ui`): create a new lightweight workflow or job (e.g.,
.github/workflows/smoke-rspack2.yml) that installs Node 22.12.0, runs the repo
build (npm/yarn build), runs a small script or test (e.g., a new script
"smoke:rspack2" in package.json) that imports the built bundles and asserts
basic runtime behavior (bundle loads without runtime errors and exports expected
symbols), and fail the job on any error; ensure the workflow runs on PRs and
include the new smoke script and any minimal test file under test/smoke or
tests/smoke so the CI actually exercises the new Rspack 2 output before merging.
In `@pnpm-workspace.yaml`:
- Around line 50-51: The exception currently whitelists the entire scope token
'@rspack/*', which is too broad; replace that entry with explicit
package+version pins for only the four newly added 2.0.0 packages (e.g.,
'@rspack/package-name@2.0.0') so only those exact artifacts bypass the 48h gate,
and keep the existing TODO comment about removing the pins once 2.0.0 is older
than 48h.
---
Outside diff comments:
In `@packages/clerk-js/rspack.config.mjs`:
- Around line 2-518: The PR introduces a major rspack-based bundling change but
lacks migration/verification tests; add automated smoke tests that build and
validate each declared variant (use variants object keys and entryForVariant,
prodConfig and devConfig outputs) to CI: create test scripts that invoke the
rspack build for clerkBrowser, clerkLegacyBrowser, clerkNative, clerk (ESM/CJS)
and clerkNoRHC variants, assert successful exit and presence of expected output
files (check output.filename/library type for commonjs/module/umd and chunking
behavior), and add these tests to the repository CI pipeline so they run on PRs
before merge.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 28eb5570-4ee1-4362-ae85-fc2dc0f1f50b

📥 Commits

Reviewing files that changed from the base of the PR and between 8a25c6a and 0b488fe.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (9)

• .changeset/rspack-2-upgrade.md
• .nvmrc
• package.json
• packages/clerk-js/package.json
• packages/clerk-js/rspack.config.mjs
• packages/clerk-js/turbo.json
• packages/ui/package.json
• packages/ui/rspack.config.js
• pnpm-workspace.yaml

[github-actions]

Break Check: no API changes detected across the tracked packages.

_{Last ran on 94cc5fb. Pushes that change no tracked declarations (no API surface change vs. base) are skipped and don't update this comment.}

[coderabbitai]

🧹 Nitpick comments (1)

packages/shared/src/react/query/useQuery.ts (1)

36-41: ⚡ Quick win

Add JSDoc documentation for the public API function.

The useClerkQuery function is exported and part of the public API, but currently has an empty JSDoc comment. As per coding guidelines, public APIs should be documented with @param, @returns, and @example tags.

📝 Suggested JSDoc documentation

 /**
- *+ * Hook to execute a Clerk-specific query using TanStack Query patterns.+ *+ * `@param` options - Query configuration options including queryKey, queryFn, and other TanStack Query options+ * `@returns` Query result with data, error, loading, and fetching states+ *+ * `@example`+ * ```tsx+ * const { data, error, isLoading } = useClerkQuery({+ * queryKey: ['user', userId],+ * queryFn: () => fetchUserData(userId),+ * enabled: !!userId,+ * });+ * ```
*/
export function useClerkQuery(options: UseQueryOptions) {
return useBaseQuery(options, QueryObserver);
}

As per coding guidelines: "All public APIs must be documented with JSDoc".

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/shared/src/react/query/useQuery.ts` around lines 36 - 41, Add a
proper JSDoc block above the exported function useClerkQuery describing its
purpose, a `@param` for the options parameter (type UseQueryOptions), a `@returns`
describing the query result shape, and an `@example` showing typical usage (e.g.,
queryKey, queryFn, enabled). Reference the implementation details by mentioning
useBaseQuery and QueryObserver so the docs note that useClerkQuery delegates to
useBaseQuery(options, QueryObserver). Keep the comment concise and follow
existing project JSDoc style.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@packages/shared/src/react/query/useQuery.ts`:
- Around line 36-41: Add a proper JSDoc block above the exported function
useClerkQuery describing its purpose, a `@param` for the options parameter (type
UseQueryOptions), a `@returns` describing the query result shape, and an `@example`
showing typical usage (e.g., queryKey, queryFn, enabled). Reference the
implementation details by mentioning useBaseQuery and QueryObserver so the docs
note that useClerkQuery delegates to useBaseQuery(options, QueryObserver). Keep
the comment concise and follow existing project JSDoc style.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eed67afe-f65b-45d3-b58c-ec5a0a59ad5e

📥 Commits

Reviewing files that changed from the base of the PR and between 8fd4764 and 71991d7.

📒 Files selected for processing (3)

• packages/clerk-js/bundlewatch.config.json
• packages/shared/src/loadScript.ts
• packages/shared/src/react/query/useQuery.ts

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

packages/clerk-js/package.json (1)

120-122: ⚠️ Potential issue | 🟠 Major

Fix engines.node to match Rspack 2’s required minimum.

packages/clerk-js/package.json sets engines.node to >=20.9.0, but Rspack 2 requires Node minimum 20.19.0 (or 22.12.0). Update the engines.node range to match (either >=20.19.0 or your chosen >=22.12.0 standard).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@packages/clerk-js/package.json` around lines 120 - 122, Update the
package.json engines.node field to meet Rspack 2’s minimum: change the
"engines.node" value from ">=20.9.0" to either ">=20.19.0" (or your chosen
stricter baseline like ">=22.12.0") so the project declares a compatible Node.js
range; locate and edit the "engines.node" entry in the package.json manifest
(key: engines.node) and commit the updated range.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@packages/clerk-js/package.json`:
- Around line 120-122: Update the package.json engines.node field to meet Rspack
2’s minimum: change the "engines.node" value from ">=20.9.0" to either
">=20.19.0" (or your chosen stricter baseline like ">=22.12.0") so the project
declares a compatible Node.js range; locate and edit the "engines.node" entry in
the package.json manifest (key: engines.node) and commit the updated range.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository YAML (base), Repository UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: dd59d800-11e7-4b80-9ac8-656f48f8b059

📥 Commits

Reviewing files that changed from the base of the PR and between e1714aa and 61d422e.

📒 Files selected for processing (2)

• packages/clerk-js/bundlewatch.config.json
• packages/clerk-js/package.json

✅ Files skipped from review due to trivial changes (1)

• packages/clerk-js/bundlewatch.config.json

[github-actions]

API Changes Report

Generated by Break Check on 2026-06-12T12:06:36.032Z

Summary

Metric	Count
Packages analyzed	19
Packages with changes	0
🔴 Breaking changes	0
🟡 Non-breaking changes	0
🟢 Additions	0

Note
Break Check could not snapshot 1 subpath; the diff below excludes them.

• @clerk/astro ./env: Internal Error: Unable to determine module for: /home/runner/_work/javascript/javascript/packages/astro/env.d.ts You have encountered a software defect. Please consider reporting the issue to the maintainers of this application.

No API Changes Detected

All packages have stable APIs with no detected changes.

---

Report generated by Break Check

_{Last ran on c31eb18.}

[dstaley]

lgtm