feat: merge next-on-netlify into the core plugin repo #106
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.
This looks like a huge PR, but what's happening here is that we're merging the
next-on-netlify
repo into this build plugin for a few reasons:next-on-netlify
as a standalone package. Everything it does is handled by this plugin with less setup overhead, so moving forward we're making@netlify/plugin-nextjs
the Official Recommendation™ for how to build Next.js sites on NetlifyThe merge of the
next-on-netlify
package also paves the way for us to make the Next.js development experience on Netlify even more seamless through automatic installs for new Next.js sites. This does not have any effect on existing sites.Because that's a big change in behavior, we're going to treat this as a breaking change despite the fact that there are no actual breaking changes in the code.
Check out the updates to the changelog for more information on how this affects existing sites (tl;dr it doesn't unless you want it to) and how things will work with new sites going forward.
We're super excited about this change, and we hope you will be, too!