Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(nextjs): Let Next.js handler serve public/ folder #16318

Merged
merged 1 commit into from
Apr 14, 2023

Conversation

ndcunningham
Copy link
Contributor

Current Behavior

Custom header are not applied to files in the public/ folder by the dev server or the production server

Expected Behavior

Files in the public/ folder should have custom headers applied.

Related Issue(s)

Fixes #16237

@vercel
Copy link

vercel bot commented Apr 14, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
nx-dev ⬜️ Ignored (Inspect) Apr 14, 2023 6:38pm

@jaysoo jaysoo merged commit d54f848 into nrwl:master Apr 14, 2023
@ndcunningham ndcunningham deleted the fix/nextjs-public-serving branch April 14, 2023 19:40
peppoasap pushed a commit to peppoasap/nx that referenced this pull request Apr 18, 2023
Co-authored-by: Louis DeScioli <louis@spatial.io>
@github-actions
Copy link

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Next.js custom headers not being applied to files in public folder
2 participants