We want to make it clear that it's a Chromatic project (@chromaui wasn't doing that, thus the change of npm org), so people understand what Chromatic is.
We have a naming scheme under the @chromatic-com namespace where the second word is the tool we are integrating with (e.g. @chromatic-com/playwright). This is consistent with that.
📦 Published PR as canary version: 1.0.1--canary.163.7c12524.0
:sparkles: Test out this PR locally via:
```bash
npm install @chromatic-com/storybook@1.0.1--canary.163.7c12524.0
# or
yarn add @chromatic-com/storybook@1.0.1--canary.163.7c12524.0
```
The rationale for the name change:
@chromauiwasn't doing that, thus the change of npm org), so people understand what Chromatic is.We have a naming scheme under the
@chromatic-comnamespace where the second word is the tool we are integrating with (e.g.@chromatic-com/playwright). This is consistent with that.📦 Published PR as canary version:
1.0.1--canary.163.7c12524.0:sparkles: Test out this PR locally via: ```bash npm install @chromatic-com/storybook@1.0.1--canary.163.7c12524.0 # or yarn add @chromatic-com/storybook@1.0.1--canary.163.7c12524.0 ```