-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Next.js 10 #188
Comments
The plan it to get there ASAP. The only major difference is that I need to replace our custom i18n routing with the native one. There might be functional regressions there so this needs to be tested thoroughly. And use/showcase the |
Well Amplitude is not quite free right? I think we should embrace Next.js Analytics as well. And we might need to get rid of And update all i18n routes utilities in favor of the new automatic resolving of href. I'm super excited about it. :) |
Amplitude is free until 10 million events a month. So, it's not too bad either. (and more effective if you need to consolidate stats from several sites) Definitely gonna replace GraphCMSAsset and AirtableAsset with Image, not sure if I'll wrap the Image yet (to deal with custom business rules) or replace them altogether yet. I hope I can do all those things within the end of the week-end. |
One preset has been upgraded to Next.js 10. I encountered a few issues, and there are non-backward compatible changes to take care of, but nothing really complicated once you understand the underlying issues. I'm going to make a PR for the other preset. |
The other preset has been upgraded to Next.js 10. Note that in order to make is easy to cherry-pick/rebase those changes, I've only done what's required for the upgrade to function normally. There is still a lot of work to be done to benefit from the actual features, but those will be done in separated commits/PRs. |
FA icons have been refactored into a distinct file. |
Could you specify what this work means? Refactor |
Yeah, this and i18n, I18nLink, etc. There is one regression with the native i18n though, see vercel/next.js#17078 (comment) |
Ok, it'd be great to create issues for each single feature that needs to be implemented, to keep things more organized and easy to track. |
True. I first thought I'd be able to quickly change the NRN implementation about i18n routing and asset/image, but I've met some drawbacks and changed my mind.
I'm closing this, NRN has been upgraded to Next.js 10 successfully, and both presets have been upgraded. Further upgrades will be done in distinct PRs. |
What about automatic resolving of href? |
What's the plan to get NRN up to Next.js 10? https://nextjs.org/blog/next-10
There are a lot of new features:
What's been done:
v2-mst-aptd-at-lcz-sty
has been upgraded to Next.js 10 Upgradev2-mst-aptd-at-lcz-sty
preset to Next.js 10 #189v2-mst-aptd-gcms-lcz-sty
has been upgraded to Next.js 10 Upgradev2-mst-aptd-gcms-lcz-sty
preset to Next.js 10 #190704c2e0
(#86)v2-mst-aptd-at-lcz-sty
upgrades:v2-mst-aptd-at-lcz-sty
preset) #191v2-mst-aptd-gcms-lcz-sty
upgrades:v2-mst-aptd-gcms-lcz-sty
preset) #192What's left to do:
The text was updated successfully, but these errors were encountered: