This repository was archived by the owner on May 10, 2021. It is now read-only.
Add support for a custom _redirects file #21
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Since _redirects always takes precedence over netlify.toml, allowing a custom _redirects file to be prepended to the published one is the only way to force a redirect of a path that matches content handled by next-on-netlify. This can be useful when using netlify to redirect from one domain to another.
| This is awesome! Thank you, @etrepum, for another fantastic contribution! It's really great to have you improve |
| Happy to help! Your project saved me a lot of time in figuring out how to make things work in such a seamless way. The hardest part is figuring out how to match the style, I'm accustomed to automatic formatting with prettier these days :) |
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Since _redirects always takes precedence over netlify.toml,
allowing a custom _redirects file to be prepended to the
published one is the only way to force a redirect of a path that
matches content handled by next-on-netlify. This can be
useful when using netlify to redirect from one domain to another.