*** deprecating next-on-netlify *** (info & feedback)
lindsaylevine opened this issue · 1 comments
beloved NoN users! it's been a pleasure serving you here on this repo, born and raised by friend and inspiration @FinnWoelm, but it's time to deprecate next-on-netlify in favor of its successor, the Essential Next.js plugin - built and supported by the same people who have been maintaining NoN.
this issue will be the primary place for NoN users to ask questions and give feedback about us deprecating next-on-netlify and moving to the plugin. we know there are NoN users who prefer the standard manual NoN setup, and we're committed to making sure the plugin experience suits your needs as well.
testing the plugin with next-on-netlify embedded
right now, we have a canary release of the plugin that merges next-on-netlify into its source. that said, all of the internals of NoN will live on, just inside the plugin :).
please feel free to test out the canary release by installing the plugin via npm i @netlify/plugin-nextjs@canary and adding it to your netlify.toml file like so:
[[plugins]]
package = "@netlify/plugin-nextjs"
next steps
we plan to release the new plugin, with next-on-netlify merged in, at or around the same time that we start automatically installing the plugin for next.js sites on netlify. this is also when the new plugin name (essential next.js plugin) will become more widely known/used, and this is when we will formally deprecate next-on-netlify and archive this repo.
at that time, we will transfer open NoN issues to the plugin repo.
please let us know how we can best support you moving over to the plugin!
The last year has been a wonderful journey for next-on-netlify ❤️
next-on-netlify really has come a very long way, from the small prototype project that it started as, all the way to being adopted by @netlify, and now soon being automatically installed with zero-config. And even though it's always sad to say goodbye, in this case I am extremely excited for what's to come. It's been an immense pleasure working with the very talented @lindsaylevine and her colleagues at Netlify over the last couple months. Let me tell you, this project (and support for Next.js on the Netlify platform in general) is in very good hands.
Lastly, I can say with absolute certainty that next-on-netlify would not have been possible without the numerous contributions, detailed bug reports, and supportive messages from all of you. This was especially true during the early phases of the project, before Netlify got involved. Thank you, next-on-netlifiers! ❤️