Fix Documentation Styles on Subpath Deployment#32
Conversation
- Updated `docs/next.config.mjs` to include `basePath` and `assetPrefix` for production builds to ensure correct asset loading on GitHub Pages under the `/typescript` subpath. - Modified root `next.config.ts` to exclude the `/typescript/` subpath from global security headers using a negative lookahead regex. - Added a permissive CSP meta tag to the documentation layout to allow Google Fonts and inline styles required by Nextra.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
1 participant
The documentation site at
cur8d.dev/typescriptwas failing to load styles due to incorrect asset pathing (root-relative vs. subpath-relative) and restrictive CSP headers from the root application.This PR implements two fixes:
basePathandassetPrefixin the documentation's Next.js config to correctly reference assets under the/typescriptsubpath in production.PR created automatically by Jules for task 15904934647840445646 started by @amrabed