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
With Nuxt's layer/extends mechanism, my idea is that folks could extend from abstract layers or apps, and the only "main" app could use Storybook to compile all components from the hierarchy into a only single SB instance.
I have a separate Nuxt module writing out the layer paths (i.e., on nuxt prepare), then use it in SB main.
Feels like storybook-vue/nuxt could easily include these paths by default instead of the user defining it, although its debatable if it should.. maybe it would be good to just write out the layers template for users to use:
With Nuxt's layer/extends mechanism, my idea is that folks could extend from abstract layers or apps, and the only "main" app could use Storybook to compile all components from the hierarchy into a only single SB instance.
I have a separate Nuxt module writing out the layer paths (i.e., on nuxt prepare), then use it in SB main.
Feels like storybook-vue/nuxt could easily include these paths by default instead of the user defining it, although its debatable if it should.. maybe it would be good to just write out the layers template for users to use:
The text was updated successfully, but these errors were encountered: