Change npm organisation from kadira to storybook

[ndelangen]

We will be publishing to the storybook organisation on npm, our code should reflect that.

• Change package names
• Change info in package.json like repository etc
• Change documentation
• Deprecate existing @kadira packages, or at least the addons?

[aaronmcadam]

I recently wrote a codemod for updating imports. Let me know and I'll raise a PR later.

[ndelangen]

I'd love for this PR to happen and would merge it in a heartbeat.
I think webpack 2 is done (need to do more regression testing) so I think we've got only this to do before doing a alpha.01 release! 🚢

[aaronmcadam]

@ndelangen Have a play with this codemod in AST explorer and let me know if it's alright.

[ndelangen]

Looks about right to me, did some superficial testing and it seems to preserve other dependencies. Are you going to do a PR? 🥇

[aaronmcadam]

Yeah I'll raise one soon @ndelangen

[vovacodes]

@ndelangen is it going to be @storybook/storybook or just storybook?
I can prepare the changes to package.json and docs in the meanwhile

[ndelangen]

Uhm good question, perhaps something I should throw into the #roadmap on slack: but i was kinda thinking about @storybook/core

[ndelangen]

@storybook/storybook it is 😆

[vovacodes]

Got it!

[ndelangen]

Completed