Fix repo path validation for framework-specific route segments

[sentry]

This PR addresses an issue where certain framework-specific file paths, particularly those used in SvelteKit for dynamic routes (e.g., [postId]), were being rejected by the isValidRepoPath utility due to an overly restrictive regex.

The REPO_PATH_SEGMENT_PATTERN regex in src/utils/repo-path.ts previously did not allow characters like [, ], (, ), and @. This caused validation errors when attempting to load example files from frameworks that utilize these characters in their routing conventions.

Changes Made:

• Updated REPO_PATH_SEGMENT_PATTERN in src/utils/repo-path.ts to include [, ], (, ), and @ characters. The + character was also explicitly added to support SvelteKit's +page.svelte convention.
• Added new test cases to tests/repo-path.test.ts to ensure that SvelteKit bracket-style dynamic routes, Next.js/Remix parenthesis route groups, and @-prefixed directories are now correctly validated as valid repository paths.

Fixes TANSTACK-COM-3ZT

_{This PR was automatically generated by Sentry. You can adjust this setting at any time.}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	tanstack-com	b793716	Commit Preview URL Branch Preview URL	Aug 29 2026, 11:03 PM