Hallelujah Angular users! π We just merged a last-minute Angular PR for Ivy rendering support in Storybook (huge props to @ThibaudAv @kroeder for making this happen!). This change is available in SB 6.3.0-beta.10 and above.
We're very late in the Storybook 6.3 cycle (RC on Monday!), so we desperately need your testing help. If it's too destabilizing, we need to roll it back and release in 6.4.
If you're installing Storybook from scratch, run this in your project root:
npx sb@next init
If it's an Angular 12 project, you may also need to add webpack as a top-level dependency:
npm install webpack --save-dev
If you're upgrading an older version of Storybook, first run this in your project root:
npx sb@next upgrade --prerelease
Then install storybook-addon-angular-ivy
and add it to your .storybook/main.js
config:
npm install storybook-addon-angular-ivy --save-dev
// .storybook/main.js
module.exports = {
addons: ['storybook-addon-angular-ivy'],
};
We'd greatly appreciate help testing this update on your Angular Ivy projects.
The biggest change is around how we render Angular stories both in the Canvas and Docs views, and whether switching between stories & docs tabs works well in all cases.
To verify your stories are actually getting rendered in Ivy, you can open the browser dev tools & type ng
in the console. If it contains more than 3 properties, you're good.
If you upgrade your project and run into problems, please file a GitHub issue on the Storybook repo.
- If the problems are rendering-related please mention "Angular Ivy" in the title
- If the problems are Angular 12 / webpack related, please mention "Angular Webpack5" in the title
Thank you so much for your help to get this out the door.
We will do our best to provide rapid support & fixes to Angular Ivy & webpack5-related issues.
We also have an #angular
channel in the Storybook Discord, where we can provide interactive support.
If we find any blockers that we don't think we can resolve by the 6.3 target release date (June 23) we may roll back the Ivy changes.
We've tested this in our fairly large Angular library that uses Storybook. We have not found any issues yet!
Thanks for the work to make this happen!