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
Easiest fix is to ensure this fragment appears in every packages/*/package.json:
{
"repository": "system-ui/theme-ui"
}
Additional context
This makes it more difficult to configure tools like Renovate, which use the repository metadata to identify packages that live in the Theme UI monorepo and upgrade them in lockstep.
There is support in the package.json spec for specifying the directory for each package, like so:
Thanks for merging; I also filed renovatebot/renovate#10281, so Renovate now has built-in support for Theme UI, which will work correctly as soon as v0.9.2 is released.
Describe the bug
Some packages, like @theme-ui/color, don't include repository metadata on NPM.
To Reproduce
Compare these two NPM packages:
Only the first package lists its repository as https://github.com/system-ui/theme-ui.
Expected behavior
All monorepo packages list their repository as https://github.com/system-ui/theme-ui.
Easiest fix is to ensure this fragment appears in every
packages/*/package.json
:Additional context
This makes it more difficult to configure tools like Renovate, which use the repository metadata to identify packages that live in the Theme UI monorepo and upgrade them in lockstep.
There is support in the
package.json
spec for specifying the directory for each package, like so:But I don't see any tooling that uses this much more verbose format, so I'm not sure the complexity adds anything.
Let me know the preferred format and I'm happy to submit a PR, looks like an easy low-risk update.
The text was updated successfully, but these errors were encountered: