-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
change NPM organisation from kadira to storybook in code #996
Conversation
Codecov Report
@@ Coverage Diff @@
## master #996 +/- ##
==========================================
+ Coverage 12.51% 12.57% +0.05%
==========================================
Files 196 200 +4
Lines 4458 4478 +20
Branches 713 714 +1
==========================================
+ Hits 558 563 +5
- Misses 3269 3283 +14
- Partials 631 632 +1
Continue to review full report at Codecov.
|
36eca2a
to
41f9b97
Compare
2adbf62
to
3a7e455
Compare
3a7e455
to
144c269
Compare
@ndelangen Can we confirm what we want the published name these packages to be? Should we drop all |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to add the codemod as a package? I'd think not.
So I've been trying this, but it would appear that in order to get this to work, all packages must at least have been published once on npm, in order for lerna to be able to bootstrap. |
It would be useful for users to migrateOn 8 May 2017 4:22 pm, Norbert de Langen <[email protected]> wrote:@ndelangen commented on this pull request.
Do we need to add the codemod as a package? I'd think not.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
|
Lerna doesn't need the packages to be published to bootstrap. Tests will fail though where they reference the new package names. |
That's what I'm hearing from lerna maintainers, however check the travis logs, bootstrap does fail...
Right, I'd move them somewhere else though, maybe |
I'd personally like to remove the |
@ndelangen I think we should only have So the directory structure would go from this: addon-actions
addon-comments
addon-graphql
addon-info
addon-knobs
addon-notes
addon-options
addons
channel
channel-postmessage
channel-websocket
codemod
decorator-centered
getstorybook
react-native-storybook
react-storybook
storybook-ui
storyshots to this: addon-actions
addon-comments
addon-graphql
addon-info
addon-knobs
addon-notes
addon-options
addons
channel
channel-postmessage
channel-websocket
codemod
decorator-centered
getstorybook
native-storybook
storybook
ui
storyshots |
@ndelangen regarding the codemod, I understand where you're coming from regarding keeping If we move it elsewhere, we'll have to manually manage publishing it. We might be able to make it work by setting the |
Hi! And is it clear that |
Good suggestion! I'm already using the |
Do you prefer |
I agree that |
I was trying to aim for parity between the directory names on disk and the package names on |
Ok, so the latest consensus is:
|
Sorry to through my 2ct in the mix again... Here's my suggestion:
|
To all those watching this PR, I've added the name changes to the PR description. |
Okey And wouldn't it better to rename |
@usulpro I think we should have the same prefix for these namespaced packages so that it's easier to see that packages are related visually. I don't mind moving |
How do you like the idea (if it still possible) to move all addons into a separate folder |
# Conflicts: # examples/cra-storybook/package.json # examples/cra-storybook/src/stories/index.js # examples/test-cra/package.json # examples/test-cra/src/stories/index.js # packages/addon-actions/.storybook/addons.js # packages/addon-comments/.storybook/addons.js # packages/addon-comments/package.json # packages/addon-info/.storybook/addons.js # packages/addon-info/example/story.js # packages/addon-info/package.json # packages/addon-knobs/.storybook/addons.js # packages/addon-knobs/README.md # packages/addon-notes/README.md # packages/addon-notes/package.json # packages/addon-options/.storybook/addons.js # packages/getstorybook/generators/METEOR/template/.stories/index.js # packages/getstorybook/generators/REACT/template/stories/index.js # packages/getstorybook/generators/REACT_NATIVE/template/storybook/addons.js # packages/getstorybook/generators/REACT_NATIVE/template/storybook/stories/index.js # packages/getstorybook/generators/REACT_SCRIPTS/template/src/stories/index.js # packages/react-native-storybook/docs/manual-setup.md # packages/react-native-storybook/package.json # packages/react-native-storybook/src/index.js # packages/react-native-storybook/src/server/addons.js # packages/react-storybook/demo/package.json # packages/react-storybook/demo/src/stories/index.js # packages/react-storybook/src/client/index.js # packages/react-storybook/src/server/addons.js # packages/storyshots/package.json # packages/storyshots/stories/required_with_context/Button.stories.js # packages/storyshots/stories/required_with_context/Welcome.stories.js
…ructure CHANGE folder structure && CHANGE package-names
☁️ Nx Cloud ReportCI is running/has finished running commands for commit bcbc570. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
Issue: #773
Blocked by
#1004,
#1008What I did
Created the codemod
How to test
Run unit tests
TODO
storybook-
prefixesgetstorybook/generators
LICENSE
sCODE_OF_CONDUCT
sREADME
badge URLsreact-storybook/src/server/track_usage.js
New Package directories and names