Try storybook v6's “composition” mode
Closed, ResolvedPublic
Actions

Assigned To

Authored By

	• Pablo-WMDE
	Jul 21 2020, 2:00 PM

Description

References:

		Status	Subtype	Assigned	Task
		Resolved		None	T257812 Set up component library infrastructure
		Resolved		• Pablo-WMDE	T258494 Try storybook v6's “composition” mode

• Pablo-WMDE created this task.

port-based include requires for both storybooks to be web hosted
- and CORS is a thing
to allow for a storybook to be composed (used in another one), it needs puppeteer-based post-build treatment (loading is done via a stories.json which - for reasons - is not part of normal storybook build)
- given this line I may have done something wrong...

vue-components has its own storybook which gets published on chromatic
docs' storybook composes vue-components' stories into itself via HTTP (different domain)

versioning (so that both storybooks use the same version, or at least communicate that they could be off)

vue-components has its own storybook which gets copied into a subfolder of the docs storybook
docs' storybook composes vue-components' stories into itself by loading the subfolder (same domain)

chromatic UI review is not available without publishing vue-components storybook as a dedicated project - can be mitigated by copying into docs and publishing separately

conceptual decision: who includes whom? (docs the vue-components [as demoed], or the other way around)
somehow this made me question the idea of the docs package. Why didn't we just put this in the project root?
chromatic seems to be somewhat unhappy to have two projects for the same repository
docs chromatic is unhappy if we delete the dummy component (which is unneeded) because it think there are 0 stories there
(low prio in my eyes) getting dev to work in "composition" mode (no X11 in the container is a problem, as it prevents the consumed storybook to successfully publish)