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
Currently when @web/dev-server-storybook is used in the Monorepo particularly with yarn workspaces in which the dependencies are managed centrally instead of package-level, the building of the storybook feature breaks on the following issue:
node_modules/@web/dev-server-storybook/node_modules/babel-plugin-bundled-import-meta/index.js:68
throw new Error('Does not match any mappings or bundleDir.');
From quick investigation, the change in rollup base config, by adding support for packageDir, would fix the issue.
The text was updated successfully, but these errors were encountered:
We intend to deprecate @web/dev-server-storybook in favor of @web/storybook-builder.
Let's maybe pair up sometime this or next week and try a new @web/storybook-builder?
I think it should be better to monorepo.
I can make a prerelease for you with our internal config and addons and help to set it up. Actually curious how it's gonna work in a big project and monorepo, also how the migration scripts will work and such
Currently when
@web/dev-server-storybook
is used in the Monorepo particularly with yarn workspaces in which the dependencies are managed centrally instead of package-level, the building of the storybook feature breaks on the following issue:From quick investigation, the change in rollup base config, by adding support for
packageDir
, would fix the issue.The text was updated successfully, but these errors were encountered: