-
Notifications
You must be signed in to change notification settings - Fork 87
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
Custom Netlify Redirects Overwritten #158
Comments
@juanpprieto hey! the plugin doesn't override - it reads your custom redirects from the root of your project. if you put your |
@lindsaylevine amazing that worked! thanks I had a feeling it was simply ignoring it (from being in the wrong path) rather than overwriting it. Feel free to close and thanks once again for the quick response. |
@juanpprieto haha yeah of course!!! happy to help!! |
I'm glad I've found your comment @lindsaylevine ! I think it can be confusing for someone following the docs like me:
Maybe we can add a note there that it may vary if you're using a framework like Next.js since we're not using the "publish directory" in here. |
* feat: remove x-nextjs-cache header and add Cache-Status instead * chore: rename cache name from 'Next Cache' to 'Next.js' * test: adjust test after removing x-nextjs-cache header and adding cache-status * test: cache-status can have multiple values, adjust assertions for that * test: e2e quirks worked out --------- Co-authored-by: Rob Stanford <me@robstanford.com>
Describe the bug
netlify-plugin-nextjs seems to overwrite custom
_redirects
file rulesTo Reproduce
Steps to reproduce the behavior:
public/_redirects
out_publish/_redirects
includes only# Next-on-Netlify Redirects
....Expected behavior
I would expect to see the custom redirect rules merged in at the very top of the
out_publish/_redirects
fileVersions
"next": "^10.0.3"
"@netlify/plugin-nextjs": "^3.0.0"
If you're using the CLI to build
Mac
netlify-cli@3.10.5
If you're using file-based installation
Custom _redirects
The text was updated successfully, but these errors were encountered: