You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: upgraded and auto migrated storybook and related dependencies
Upgraded and auto migrated storybook and related dependencies
HCRC-178.
The Storybook related files and dependencies were updated with
```shell
npx storybook@latest upgrade
```
It ran a automated migration script that resulted to following:
```
◇ Checking the health of your project(s)..
│
│ Your Storybook project looks good!
│
◇ The upgrade is complete!
│
│ Your project(s) have been upgraded successfully! 🎉
│
│ If you want to learn more about the automigrations that executed in
your
│ project(s), please check the following links:
│
│ • upgrade-storybook-related-dependencies
│ • addon-globals-api
│ • consolidated-imports
│ • remove-addon-interactions
│ • renderer-to-framework
│ • remove-essential-addons
│
│ For a full list of changes, please check our migration guide:
│ https://storybook.js.org/docs/releases/migration-guide?ref=upgrade
```
----
fix: exports, storybook, babel, jest and msw synergy
1. Install a new storybook (to fix critical security issues reported by
Dependabot). Used `npx storybook@latest upgrade` to run an automated
migration tool.
2. Storybook upgrade and migration resulted in some type issues and
issues starting the storybook. Export clauses needed "type" addition to
the statement when the re-exported object was a type.
3. MSW needed an update in order to fix the Storybook issues. Upgraded
MSW and migrated the old mocks to support new syntax and rules.
4. Some new linting issues and deprecation warnings appeared and also
the JEST environment needed some reconfiguration. Jest now had some
problems with JSDom / ESM overlapping in same project. Fixed the type
issues.
5. In order to fix the Jest environment, babel needed some
reconfiguration.
|`yarn dev`| Starts storybook environment that can be used for developing components. ||
@@ -62,7 +61,6 @@ The general requirements for new Component development:
62
61
63
62
**NOTE: To manually publish a new version to the NPM, you will need the credentials that can be found from the City of Helsinki Culture and Leisure's Vault-service.**
64
63
65
-
66
64
### Development environments
67
65
68
66
You can use docker local environment for development:
0 commit comments