Page MenuHomePhabricator

Re-evaluate location of the primary component library repository
Closed, ResolvedPublic

Description

Things to consider:

  • docs publishing
  • actions (for 3rd party stuff, modern docker images, ...)
  • automated dependency updates for package.json
  • branch hosting/grooming

Event Timeline

We went with a

  • github-hosted
  • monorepo
    • reap the benefits of clear package separation while still allowing direct re-use across packages without release (enabled by lerna)
    • synced version numbers of packages (e.g. on tokens and vue-components) on release, c.f. vue-cli, will hopefully help consuming applications (likely using both the component library and design token packages) to keep them aligned
    • needed a name acting as an umbrella led to creation of a new repository instead of re-using "wikibase/vuejs-components" or "wmde/wikit-css/" (a rename would have been due for either, so we decided to keep them for historical purposes instead)

The decision is also documented in this ADR.

There is not much to review here. The ADR already exists, I added what I could think of in the comment above.