next 13 support
See original GitHub issueDescribe the bug
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: storybook-addon-next@1.6.9
npm ERR! Found: next@13.0.0
npm ERR! node_modules/next
npm ERR! next@"13.0.0" from the root project
npm ERR! peer next@"^8.1.1-canary.54 || >=9.0.0" from next-seo@5.8.0
npm ERR! node_modules/next-seo
npm ERR! next-seo@"5.8.0" from the root project
npm ERR! 1 more (next-sitemap)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer next@"^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0" from storybook-addon-next@1.6.9
npm ERR! node_modules/storybook-addon-next
npm ERR! dev storybook-addon-next@"1.6.9" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: next@12.3.1
npm ERR! node_modules/next
npm ERR! peer next@"^9.0.0 || ^10.0.0 || ^11.0.0 || ^12.0.0" from storybook-addon-next@1.6.9
npm ERR! node_modules/storybook-addon-next
npm ERR! dev storybook-addon-next@"1.6.9" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See C:\Users\shala\AppData\Local\npm-cache\eresolve-report.txt for a full report.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\shala\AppData\Local\npm-cache\_logs\2022-10-25T22_25_34_802Z-debug-0.log
npm ERR! code 1
npm ERR! path E:\source\vizesizgezi
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c cd dataset && npm install && cd ../frontend && npm install && cd ../migrator && npm install && cd ../tasks && npm install && cd ../tools/image_gen && npm install && cd ../..
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\shala\AppData\Local\npm-cache\_logs\2022-10-25T22_25_21_001Z-debug-0.log
Your minimal, reproducible example
n/a
Steps to reproduce
upgrade next to 13.0.0.
Expected behavior
should install properly
How often does this bug happen?
Every time
Screenshots or Videos
No response
Platform
any
storybook-addon-next version
1.6.9
Additional context
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:16
- Comments:9 (3 by maintainers)
Top Results From Across the Web
Blog - Next.js 13
The app directory includes support for: Layouts: Easily share UI between routes while preserving state and avoiding expensive re-renders. Server ...
Read more >Next.js 13 Support · Issue #6056 · getsentry/sentry-javascript
Problem Statement. Next. js 13 has just come out, and brings with it various changes we'll need to support. Layouts and component-level data ......
Read more >AWS Amplify Hosting announces support for Next.js 12 and 13
Today, AWS Amplify Hosting announces Next.js 12 and 13 support, including middleware, incremental static regeneration (ISR), and image ...
Read more >Deploy Next.js 13 on Netlify Today
Netlify supports Next.js 13 today. You can update your site to Next 13 and it will work on Netlify right away. All the...
Read more >iPhone 13 Pro - Apple Support
Get to know your iPhone 13 Pro. ... The front view of iPhone 13 Pro. The front camera is at the top center...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thank you all for your patience 😃
I also ran into errors with this plugin. I opted to follow the guide from storybook here to force unoptimized images. I also ran into an issue with Next 13 that the
next/linkcomponent would not render the child anchor when you pass a React element as the child (text nodes seem to work fine) - found a workaround here: https://github.com/storybookjs/storybook/issues/19813Edit: the issue with
next/linkhas been resolved in storybook v7 (still in alpha)