-
-
Notifications
You must be signed in to change notification settings - Fork 29
Support Storybook v7 for upgrading #186
Comments
I'm currently running into an issue with webpack when upgrading examples/nextv13. I'm reaching out to storybook for help on this. The code is on the https://github.com/RyanClementsHax/storybook-addon-next/tree/sb-7 branch |
So, before I even get to the stage at looking at your branch, I would expect you to at least describe the problem. |
Oh please forgive me for my poor etiquete. When I do the following
I get the following error.
I think I'm missing something simple here. It's worth noting the dependencies of the example. {
"name": "nextv13",
"private": true,
"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"storybook": "storybook dev -p 6006 -s public",
"build-storybook": "storybook build -s public",
"serve-storybook": "serve storybook-static"
},
"dependencies": {
"next": "^13.0.0",
"react": "^18.2.0",
"react-dom": "^18.2.0",
"sass": "^1.55.0"
},
"devDependencies": {
"@babel/core": "^7.19.6",
"@storybook/addon-actions": "^7.0.0",
"@storybook/addon-essentials": "^7.0.0",
"@storybook/addon-links": "^7.0.0",
"@storybook/react-webpack5": "^7.0.0-alpha.0",
"babel-loader": "^9.0.0",
"serve": "^14.0.1",
"storybook": "^7.0.0",
"storybook-addon-next": "link:../../"
}
} and the storybook config module.exports = {
stories: [
'../stories/**/*.stories.mdx',
'../stories/**/*.stories.@(js|jsx|ts|tsx)'
],
addons: [
'@storybook/addon-links',
'@storybook/addon-essentials',
'storybook-addon-next'
],
framework: {
name: '@storybook/react-webpack5',
options: {}
}
} |
This addon is no longer needed when using Storybook 7, it was turned into a dedicated framework instead. So, rather than using Or, maybe there are reasons to continue using this addon rather than the official framework? Edit: I see now you're the maintainer of this addon, and you have a note in the readme about this addon being deprecated. So I'm a little confused why you'd want to make the addon work in v7. |
The idea was to attempt to make migration easy. There are some breaking changes when going from Alas, I'm going to keep trying. It was my fault for assuming this migration would be easy and just a matter of me bumping the peer dependencies of the addon's package.json lol |
I'll let you decide if you want to upgrade this addon or not, I think the use case for a simpler migration path for users is valid, but there are of course always trade ofs. However I see in your dependencies you list |
Yeah, after considering this further, it seems that a migration would force adopting some framework anyway which defeats the purpose of what I'm trying to do here. Instead I'm considering making the migration as easy as possible with good docs and references. Before I do this, does anyone have any contrasting opinions? |
This issue has been automatically marked stale because it it received no activity for 60 days. If you wish to keep this open, please leave a comment. Thanks. |
This issue has been automatically closed because it received no activity for 60 days. If you think this was closed by accident, please leave a comment. Thanks. |
Describe the bug
storybook-addon-next
doesn't fully support storybook v7 yet, but it should to help projects migrate.Your minimal, reproducible example
N/A
Steps to reproduce
N/A
Expected behavior
N/A
How often does this bug happen?
None
Screenshots or Videos
No response
Platform
N/A
storybook-addon-next version
N/A
Additional context
No response
The text was updated successfully, but these errors were encountered: