Using getstorybook on Storybook 2.x repo

[usulpro]

The most convenient way to migrate from Storybook 2.x to Storybook 3.x is to run getstorybook as it mention in our MIGRATION.md
It works fine but there are some issues left. Fixing them we could make migration process even more comfortable for users.

How to reproduce

git clone https://github.com/sm-react/storybook-adk.git -b storybook_2.x
cd storybook-adk/
git checkout -b migration_test
npm i @storybook/cli -g
getstorybook
npm start

It´ll throw errors which should be solved manually. So the issues are:

• Doesn´t insert caret (^) in package.json. e.g.:

"@storybook/addon-knobs": "3.1.6",
"@storybook/react": "3.1.7",

expected:

"@storybook/addon-knobs": "^3.1.6",
"@storybook/react": "^3.1.7",

• Left "@kadira/storybook": "^2.33.1" in peerDependencies

expected:

change to the latest @storybook/react package

• Left "@kadira/storybook-addons": "^1.6.1" in dependencies

• Left "@kadira/react-storybook-addon-info": "^3.3.0"

• Left "@kadira/storyshots": "^2.1.0"

• Creates import infoAddon from '@storybook/react-addon-info'; instead of @storybook/addon-info

• Doesn't procces *.jsx files

[janusch]

Hey,
there is a slight confusion about the addon-info package.
I just ran the latest getstorybook command and it rewrote the addon-info imports to:
import infoAddon from '@storybook/react-addon-info';
whereas the package states that it has moved to import infoAddon from '@storybook/addon-info';
See: https://github.com/storybooks/react-storybook-addon-info

Is this the correct package? import infoAddon from '@storybook/addon-info';

Thank you in advance for clarification!

[usulpro]

@janusch the right name of this package is @storybook/addon-info
See: https://github.com/storybooks/storybook/tree/master/addons/info

[janusch]

thanks a lot for the reply!

[stale]

Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 60 days. Thanks!

[stale]

Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook!