You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[BUG] Docs content build fails on Windows: page paths use backslashes #10066
apps/docs/content/docs/introduction/index.mdx exists. The cause is in apps/docs/scripts/compile-content.ts (line 214 on staging):
constrelative=path.relative(CONTENT_ROOT,file)
On Windows, path.relative returns introduction\index.mdx. Everything derived from relative keeps the backslashes, including the page URL: the /(^|\/)index$/ replace doesn't match, so the page becomes /introduction\index. The navigation builder then looks up meta.json entries like ./introduction/index with /, finds nothing, and throws.
Because the pre-push hook runs type-check across every workspace, this blocks every push from a Windows machine, whatever the change.
To Reproduce
On Windows, clone the repo and run bun install (Node 24).
cd apps/docs
bun run content:generate
See the references missing page ./introduction/index error.
Expected behavior
The content build behaves the same on Windows as on macOS/Linux.
Proposed fix
Normalize the separator once, where relative is created:
I tested this locally on Windows: unpatched, it fails as above; patched, content:generate completes (Catalog ready: 829 pages). On macOS/Linux path.sep is already /, so it's a no-op there. Happy to open a PR.
Screenshots
Terminal output from apps/docs, bun run content:generate:
Activity
fix(docs): normalize path separators in the content build on Windows (#…