chore(nextjs,vue,nuxt): Export RedirectToTasks control component
#6546
Conversation
🦋 Changeset detectedLatest commit: e31fa63 The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
@clerk/agent-toolkit
@clerk/astro
@clerk/backend
@clerk/chrome-extension
@clerk/clerk-js
@clerk/dev-cli
@clerk/elements
@clerk/clerk-expo
@clerk/expo-passkeys
@clerk/express
@clerk/fastify
@clerk/localizations
@clerk/nextjs
@clerk/nuxt
@clerk/clerk-react
@clerk/react-router
@clerk/remix
@clerk/shared
@clerk/tanstack-react-start
@clerk/testing
@clerk/themes
@clerk/types
@clerk/upgrade
@clerk/vue
commit: |
📝 WalkthroughWalkthroughAdds a changeset entry for a patch release affecting @clerk/nextjs, @clerk/vue, and @clerk/nuxt documenting a fix: "Fix export of Estimated code review effort🎯 2 (Simple) | ⏱️ ~7 minutes Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (3)
.changeset/hot-toys-poke.md (1)
5-5: Nit: End the changeset summary with a period for consistencyMinor style tweak for consistency across release notes.
-Fix export of `RedirectToTasks` control component +Fix export of `RedirectToTasks` control component.packages/nextjs/src/index.ts (2)
15-17: Consider re-exporting the component’s props type (if available)Improves DX and aligns with “Packages should export TypeScript types alongside runtime code.”
If the props type exists, add a type re-export near this block:
export type { RedirectToTasksProps } from './client-boundary/controlComponents';Also ensure the underlying component has JSDoc so the public API remains documented per guidelines.
15-17: Add a smoke test to prevent regressions on public exportNo tests were added; a lightweight check helps catch accidental removals in future refactors.
Suggested test (adapt to your runner):
- If using Jest/Vitest:
// packages/nextjs/src/__tests__/exports.test.ts import { RedirectToTasks } from '../index'; // or from '@clerk/nextjs' if package fixture is used test('exports RedirectToTasks', () => { expect(RedirectToTasks).toBeDefined(); });
- If using tsd for type assertions:
// packages/nextjs/tsd/redirect-to-tasks.test-d.ts import { expectType } from 'tsd'; import { RedirectToTasks } from '@clerk/nextjs'; expectType<unknown>(RedirectToTasks); // refine to the actual component type if availableI can tailor this to your testing setup—want me to open a follow-up PR?
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
- Linear integration is disabled by default for public repositories
You can enable these settings in your CodeRabbit configuration.
📒 Files selected for processing (2)
.changeset/hot-toys-poke.md(1 hunks)packages/nextjs/src/index.ts(1 hunks)
🧰 Additional context used
📓 Path-based instructions (10)
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Provide meaningful error messages to developers
Include error recovery suggestions where applicable
Log errors appropriately for debugging
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Profile and optimize critical paths
Validate all inputs and sanitize outputs
Implement proper logging with different levels
Files:
packages/nextjs/src/index.ts
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Use Prettier for consistent code formatting
Files:
packages/nextjs/src/index.ts
packages/**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
TypeScript is required for all packages
Files:
packages/nextjs/src/index.ts
packages/**/*.{ts,tsx,d.ts}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Packages should export TypeScript types alongside runtime code
Files:
packages/nextjs/src/index.ts
packages/**/index.{js,ts}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Use tree-shaking friendly exports
Files:
packages/nextjs/src/index.ts
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Use proper TypeScript error types
**/*.{ts,tsx}: Always define explicit return types for functions, especially public APIs
Use proper type annotations for variables and parameters where inference isn't clear
Avoidanytype - preferunknownwhen type is uncertain, then narrow with type guards
Useinterfacefor object shapes that might be extended
Usetypefor unions, primitives, and computed types
Preferreadonlyproperties for immutable data structures
Useprivatefor internal implementation details
Useprotectedfor inheritance hierarchies
Usepublicexplicitly for clarity in public APIs
Preferreadonlyfor properties that shouldn't change after construction
Prefer composition and interfaces over deep inheritance chains
Use mixins for shared behavior across unrelated classes
Implement dependency injection for loose coupling
Let TypeScript infer when types are obvious
Useconst assertionsfor literal types:as const
Usesatisfiesoperator for type checking without widening
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Use type-only imports:import type { ... } from ...
Noanytypes without justification
Proper error handling with typed errors
Consistent use ofreadonlyfor immutable data
Proper generic constraints
No unused type parameters
Proper use of utility types instead of manual type construction
Type-only imports where possible
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)
Files:
packages/nextjs/src/index.ts
**/*.{js,ts,tsx,jsx}
📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)
Support multiple Clerk environment variables (CLERK_, NEXT_PUBLIC_CLERK_, etc.) for configuration.
Files:
packages/nextjs/src/index.ts
**/index.ts
📄 CodeRabbit Inference Engine (.cursor/rules/react.mdc)
Use index.ts files for clean imports but avoid deep barrel exports
Avoid barrel files (index.ts re-exports) as they can cause circular dependencies
Files:
packages/nextjs/src/index.ts
**/*
⚙️ CodeRabbit Configuration File
If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.
Files:
packages/nextjs/src/index.ts
.changeset/**
📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)
Automated releases must use Changesets.
Files:
.changeset/hot-toys-poke.md
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Formatting | Dedupe | Changeset
- GitHub Check: semgrep/ci
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: semgrep-cloud-platform/scan
🔇 Additional comments (2)
.changeset/hot-toys-poke.md (1)
1-5: Changeset entry correctly declares a patch for @clerk/nextjsAccurately describes the fix and follows the Changesets front-matter format.
packages/nextjs/src/index.ts (1)
15-17: LGTM: Explicit named export added and grouped correctly
- Matches PR objective.
- Maintains explicit, tree-shaking-friendly export style (no star export).
- Placement within the RedirectTo* group looks consistent/alphabetical.
| RedirectToTasks, | ||
| RedirectToUserProfile, | ||
| } from './client-boundary/controlComponents'; |
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Verify the source module actually exports RedirectToTasks
Ensure ./client-boundary/controlComponents provides a named export RedirectToTasks (and no duplicate re-exports elsewhere) to avoid runtime/import errors.
Run this script to confirm:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Verify source module exports RedirectToTasks (named export or declaration):"
rg -n -A 2 -B 2 $'\bexport\\s+\\{[^}]*\\bRedirectToTasks\\b' packages/nextjs/src || true
rg -n -A 2 -B 2 $'\bexport\\s+(const|function|class)\\s+RedirectToTasks\\b' packages/nextjs/src || true
echo -e "\n2) Confirm index.ts re-export path is present:"
rg -n -A 1 -B 1 "from './client-boundary/controlComponents'" packages/nextjs/src/index.ts
echo -e "\n3) Check for props type export (optional but recommended):"
rg -n -A 2 -B 2 $'\bexport\\s+type\\s+.*RedirectToTasks.*Props\\b' packages/nextjs/src || true
echo -e "\n4) Ensure no duplicate re-exports elsewhere:"
rg -n -A 1 -B 1 $'\bexport\\s+\\{[^}]*\\bRedirectToTasks\\b' packages -g '!packages/nextjs/src/index.ts' || trueLength of output: 1095
Missing RedirectToTasks Export in controlComponents
The re-export in packages/nextjs/src/index.ts references a RedirectToTasks symbol that isn’t defined or exported in ./client-boundary/controlComponents. This will cause a runtime import error.
• Location of broken re-export:
- File: packages/nextjs/src/index.ts
- Lines: 15–17 (includes
RedirectToTasks, … } from './client-boundary/controlComponents';)
Action required:
- Add a corresponding
export(function, class, or const) forRedirectToTasksinpackages/nextjs/src/client-boundary/controlComponents, or - Remove or correct the re-export in the index file to match the actual exports.
🤖 Prompt for AI Agents
In packages/nextjs/src/index.ts around lines 15–17 the named export
RedirectToTasks is re-exported from './client-boundary/controlComponents' but
that symbol is not defined there; either add a matching export named
RedirectToTasks (function/class/const) into
packages/nextjs/src/client-boundary/controlComponents and export it, or
remove/rename the RedirectToTasks entry in the index re-export so it matches the
actual exported names from controlComponents; ensure the exported identifier
spelling and casing match exactly and update any imports/tests that expect
RedirectToTasks.
LauraBeatris
changed the title
RedirectToTasks control componentRedirectToTasks control component
There was a problem hiding this comment.
Actionable comments posted: 2
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled
- Linear integration is disabled by default for public repositories
You can enable these settings in your CodeRabbit configuration.
📒 Files selected for processing (3)
.changeset/hot-toys-poke.md(1 hunks)packages/nuxt/src/runtime/components/index.ts(1 hunks)packages/vue/src/components/index.ts(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- .changeset/hot-toys-poke.md
🧰 Additional context used
📓 Path-based instructions (9)
**/*.{js,jsx,ts,tsx}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
**/*.{js,jsx,ts,tsx}: All code must pass ESLint checks with the project's configuration
Follow established naming conventions (PascalCase for components, camelCase for variables)
Maintain comprehensive JSDoc comments for public APIs
Use dynamic imports for optional features
All public APIs must be documented with JSDoc
Provide meaningful error messages to developers
Include error recovery suggestions where applicable
Log errors appropriately for debugging
Lazy load components and features when possible
Implement proper caching strategies
Use efficient data structures and algorithms
Profile and optimize critical paths
Validate all inputs and sanitize outputs
Implement proper logging with different levels
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
**/*.{js,jsx,ts,tsx,json,css,scss,md,yaml,yml}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Use Prettier for consistent code formatting
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
packages/**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
TypeScript is required for all packages
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
packages/**/*.{ts,tsx,d.ts}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Packages should export TypeScript types alongside runtime code
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
packages/**/index.{js,ts}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Use tree-shaking friendly exports
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
**/*.{ts,tsx}
📄 CodeRabbit Inference Engine (.cursor/rules/development.mdc)
Use proper TypeScript error types
**/*.{ts,tsx}: Always define explicit return types for functions, especially public APIs
Use proper type annotations for variables and parameters where inference isn't clear
Avoidanytype - preferunknownwhen type is uncertain, then narrow with type guards
Useinterfacefor object shapes that might be extended
Usetypefor unions, primitives, and computed types
Preferreadonlyproperties for immutable data structures
Useprivatefor internal implementation details
Useprotectedfor inheritance hierarchies
Usepublicexplicitly for clarity in public APIs
Preferreadonlyfor properties that shouldn't change after construction
Prefer composition and interfaces over deep inheritance chains
Use mixins for shared behavior across unrelated classes
Implement dependency injection for loose coupling
Let TypeScript infer when types are obvious
Useconst assertionsfor literal types:as const
Usesatisfiesoperator for type checking without widening
Use mapped types for transforming object types
Use conditional types for type-level logic
Leverage template literal types for string manipulation
Use ES6 imports/exports consistently
Use default exports sparingly, prefer named exports
Use type-only imports:import type { ... } from ...
Noanytypes without justification
Proper error handling with typed errors
Consistent use ofreadonlyfor immutable data
Proper generic constraints
No unused type parameters
Proper use of utility types instead of manual type construction
Type-only imports where possible
Proper tree-shaking friendly exports
No circular dependencies
Efficient type computations (avoid deep recursion)
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
**/*.{js,ts,tsx,jsx}
📄 CodeRabbit Inference Engine (.cursor/rules/monorepo.mdc)
Support multiple Clerk environment variables (CLERK_, NEXT_PUBLIC_CLERK_, etc.) for configuration.
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
**/index.ts
📄 CodeRabbit Inference Engine (.cursor/rules/react.mdc)
Use index.ts files for clean imports but avoid deep barrel exports
Avoid barrel files (index.ts re-exports) as they can cause circular dependencies
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
**/*
⚙️ CodeRabbit Configuration File
If there are no tests added or modified as part of the PR, please suggest that tests be added to cover the changes.
Files:
packages/vue/src/components/index.tspackages/nuxt/src/runtime/components/index.ts
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
- GitHub Check: Formatting | Dedupe | Changeset
- GitHub Check: semgrep/ci
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: semgrep-cloud-platform/scan
| @@ -19,6 +19,7 @@ export { | |||
| RedirectToSignIn, | |||
| RedirectToSignUp, | |||
| RedirectToUserProfile, | |||
| RedirectToTasks, | |||
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
LGTM: Nuxt re-export of RedirectToTasks from @clerk/vue is consistent.
This mirrors the Vue export and keeps the tree-shakable named export pattern. Please confirm dependency alignment so Nuxt consumes a @clerk/vue version that contains RedirectToTasks.
- Verify
@clerk/nuxtdepends (dep/peer) on a version range of@clerk/vuethat includes this symbol (changeset should bump as needed). - Optional: add a smoke test importing
RedirectToTasksfrom@clerk/nuxtto ensure the symbol is publicly exposed post-build.
Run this script to check dependency alignment and presence across packages:
If helpful, I can also prepare a tiny import test to assert RedirectToTasks is accessible from @clerk/nuxt.
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Confirm nuxt re-exports RedirectToTasks only once"
rg -n 'RedirectToTasks' packages/nuxt/src/runtime/components/index.ts
echo "2) Check that @clerk/nuxt depends on @clerk/vue at an appropriate version"
NUXT_PKG=$(fd -a '^package\.json$' packages/nuxt | head -n1)
if [ -n "$NUXT_PKG" ]; then
echo "Found package file: $NUXT_PKG"
if command -v jq >/dev/null 2>&1; then
jq -r '
{
dependencies: (.dependencies["@clerk/vue"] // null),
peerDependencies: (.peerDependencies["@clerk/vue"] // null),
devDependencies: (.devDependencies["@clerk/vue"] // null)
}' "$NUXT_PKG"
else
rg -n '"@clerk/vue":' "$NUXT_PKG" || true
fi
else
echo "Could not find packages/nuxt package.json" >&2
fi
echo "3) Ensure Vue index includes RedirectToTasks"
rg -n 'RedirectToTasks' packages/vue/src/components/index.ts || true
echo "4) Locate changeset mentioning RedirectToTasks"
fd -a '\.changeset/.*\.md' | xargs -r rg -n 'RedirectToTasks|@clerk/vue|@clerk/nuxt'Length of output: 1441
Confirm dependency alignment and add missing changeset
All checks pass on the re-export, but there’s no recorded changeset for this new export.
• packages/nuxt/src/runtime/components/index.ts
– RedirectToTasks is re-exported exactly once.
• packages/nuxt/package.json
– Depends on @clerk/vue via workspace:^, so it will always pull in the local Vue package.
• packages/vue/src/components/index.ts
– Exports RedirectToTasks in its public API.
• .changeset/*.md
– No changeset mentions this new export or bumps @clerk/nuxt.
Next steps:
- Add a changeset to bump
@clerk/nuxtso consumers receive the newRedirectToTasksexport. - (Optional) Add a small smoke test that imports
RedirectToTasksfrom@clerk/nuxtpost-build to verify it’s publicly exposed.
🤖 Prompt for AI Agents
In packages/nuxt/src/runtime/components/index.ts around line 22 the new export
RedirectToTasks was added but no changeset was created to bump @clerk/nuxt; add
a new .changeset markdown file that increments the @clerk/nuxt package version
(patch or minor as appropriate) and describes the new public export so consumers
receive the new symbol, and optionally add a minimal smoke test in the nuxt
package (post-build) that imports RedirectToTasks from @clerk/nuxt to verify the
re-export is publicly exposed; no code changes to the export are required, only
the changeset (and optional test) and commit.
| @@ -18,6 +18,7 @@ export { | |||
| RedirectToSignIn, | |||
| RedirectToSignUp, | |||
| RedirectToUserProfile, | |||
| RedirectToTasks, | |||
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
LGTM: Added RedirectToTasks export is correct and tree-shake friendly.
Placement is consistent with other control components and maintains the existing export style. Please verify the source symbol exists and that consumers get proper typings.
- Ensure
./controlComponentsactually exportsRedirectToTasksand that its JSDoc (public API doc) is present at the declaration site. - Consider adding a lightweight smoke test to assert
RedirectToTasksis importable from@clerk/vue.
Run this script to verify the source export and look for potential cycles:
If you want, I can draft a minimal smoke test that imports RedirectToTasks from @clerk/vue to prevent regressions.
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Ensure Vue controlComponents exports RedirectToTasks"
fd -a -t f 'controlComponents(\.ts|/index\.ts)?$' packages/vue 2>/dev/null | tee /tmp/cc_files.txt
if [ ! -s /tmp/cc_files.txt ]; then
echo "Could not find controlComponents file(s) in packages/vue" >&2
fi
rg -n 'export\s+\{[^}]*RedirectToTasks|export\s+(const|function|class)\s+RedirectToTasks' $(cat /tmp/cc_files.txt) || true
echo "2) Ensure Vue components index re-exports RedirectToTasks"
rg -n 'RedirectToTasks' packages/vue/src/components/index.ts || true
echo "3) Quick cycle smell: controlComponents importing components index"
rg -n "from ['\"]\./components['\"]" packages/vue/src || trueLength of output: 323
I’ve updated the verification script to avoid using tee (which isn’t available in this environment) and directly capture & inspect the files:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "1) Locate Vue controlComponents file(s)"
files=$(fd -t f -e ts -- 'controlComponents(\.ts|/index\.ts)?$' packages/vue 2>/dev/null)
if [[ -z "$files" ]]; then
echo "✖ Could not find any controlComponents file(s) under packages/vue" >&2
else
echo "Found:"
echo "$files"
echo
echo "Searching for RedirectToTasks export in those files:"
rg -n 'export\s+\{[^}]*RedirectToTasks|export\s+(const|function|class)\s+RedirectToTasks' $files || true
fi
echo
echo "2) Verify re-export in components index.ts"
rg -n 'RedirectToTasks' packages/vue/src/components/index.ts || true
echo
echo "3) Quick cycle check: controlComponents → components index"
rg -n "from ['\"]\./components['\"]" packages/vue/src || trueLength of output: 1184
I’ll check whether there’s a JSDoc block immediately above the RedirectToTasks declaration:
🏁 Script executed:
#!/bin/bash
set -euo pipefail
echo "Inspecting context around RedirectToTasks export for JSDoc:"
rg -n -C3 'export\s+const\s+RedirectToTasks' packages/vue/src/components/controlComponents.ts || trueLength of output: 414
Add public JSDoc for RedirectToTasks and consider a smoke test
- ✅ Verified
RedirectToTasksis exported in
packages/vue/src/components/controlComponents.ts(line 63)
and re-exported inpackages/vue/src/components/index.ts(line 21). - ✅ No import cycles detected between
controlComponentsandcomponents. ⚠️ Missing JSDoc: please add a public API doc comment immediately above the
export const RedirectToTasks = …declaration in
packages/vue/src/components/controlComponents.ts.- 🔍 Consider adding a lightweight smoke test that imports
RedirectToTasksfrom@clerk/vueto catch any regressions.
🤖 Prompt for AI Agents
In packages/vue/src/components/controlComponents.ts around line 63, the exported
RedirectToTasks constant is missing a public JSDoc comment; add a short /** ...
*/ block immediately above the export that describes what RedirectToTasks does,
marks it as public (e.g., @public), and documents any props/params or usage
note; then add a lightweight smoke test (e.g., in the library's test harness)
that simply imports { RedirectToTasks } from '@clerk/vue' to ensure the
re-export in packages/vue/src/components/index.ts stays valid.
Description
Fixes export for
RedirectToTaskscontrol componentChecklist
pnpm testruns as expected.pnpm buildruns as expected.Type of change
Summary by CodeRabbit
Bug Fixes
Chores