Skip to content

Instantly share code, notes, and snippets.

@shilman

shilman/test-package.md

Last active October 11, 2018 00:43
Show Gist options
  • Save shilman/26613afcc0c40976038454916fa8e381 to your computer and use it in GitHub Desktop.
Save shilman/26613afcc0c40976038454916fa8e381 to your computer and use it in GitHub Desktop.
Download ZIP
Publishing a test package
Raw
test-package.md

Wwhat I did to manually test some breaking changes to @storybook/cli by publishing a test-tagged package to NPM.

Publish package:

yarn bootstrap --reset --core
cd lib/cli
# edit package.json version: 4.0.0-alpha.24 => 4.0.0-test.25
npm publish --tag test --access public

NOTE: this is only publishing one package. You could also do a lerna publish of the entire monorepo using a similar --tag test approach, but I'd advise against it since this is all a hack.

Test out the new package in my project:

cd /projects/cra-example
npx @storybook/cli@test
...

Then unpublish the package within 72h:

npm unpublish @storybook/cli@4.0.0-test.25

NOTE: that npm info @storybook/cli still shows the test tag and version although it has been removed from the registry. Not sure if this is a caching issue or what, but it shouldn't affect anybody even if it hadn't been properly removed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment