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
I think @changesets/config but not 100% sure as I'm not familiar with the codebase.
Problem
We have a monorepo with packages that don't really follow a particular naming convention. Instead, they're placed in two distinct folders, let's say apps and libs. I'd like to put all of libs into linked (so that they're versioned like Babel and React packages) and all of apps into ignore as I don't want the apps to be versioned via Changesets (not right now anyway - possibly in the future?). Now I know that I can use globs but that's just for the package names, and there's no naming convention here. What I'd like to do instead is to use globby or something and pass this computed list of packages to Changesets. I can see a reference to dynamic .js configs in #533 - that would totally solve my use case. For now, I'm considering having a workaround involving a script that generates the JSON config and we run it as a commit hook to ensure it's always up-to-date.
Proposed solution
The text was updated successfully, but these errors were encountered:
Affected Packages
I think
@changesets/config
but not 100% sure as I'm not familiar with the codebase.Problem
We have a monorepo with packages that don't really follow a particular naming convention. Instead, they're placed in two distinct folders, let's say
apps
andlibs
. I'd like to put all oflibs
intolinked
(so that they're versioned like Babel and React packages) and all ofapps
intoignore
as I don't want the apps to be versioned via Changesets (not right now anyway - possibly in the future?). Now I know that I can use globs but that's just for the package names, and there's no naming convention here. What I'd like to do instead is to useglobby
or something and pass this computed list of packages to Changesets. I can see a reference to dynamic.js
configs in #533 - that would totally solve my use case. For now, I'm considering having a workaround involving a script that generates the JSON config and we run it as a commit hook to ensure it's always up-to-date.Proposed solution
The text was updated successfully, but these errors were encountered: