Closed tan-ahmed closed 2 years ago
You can upgrade it on your side, change version in package.json and install dependencies
But I don't think it's straight forward, I ran into issues doing this. Hence I am hoping you can update the entire template with latest packages. Many thanks
But I don't think it's straight forward, I ran into issues doing this. Hence I am hoping you can update the entire template with latest packages. Many thanks
I wasn't able to reproduce actual issues from the template itself with just about all deps updated: check the below package.json
file. I encountered some peer-deps versioning issues due to storybook
. If you are migrating your code take note of Next.js's migration guide, and especially next/image
and next/link
in https://nextjs.org/blog/next-13#breaking-changes.
Attached a package.json
with updated deps below. (jest
still retained at v27
for linter version compatibiility)
thanks @jhanschoo this is working now. Although I still think the overall template should be updated just to keep things upto date etc
would be good to upgrade to latest next.js, there are many improvements