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
Projects should be able to specify other project files as dependencies. This would greatly simplify some cases where packages need several subpackages that should be uploaded but are part of the same project eg a in-house/in-repo dependency or metapackages (like R2API is becoming).
When publishing, dependencies should be published before their dependents if the version number that exists in the repository is lower than the one that exists locally.
The text was updated successfully, but these errors were encountered:
I'd rephrase this as monorepo support, but that is something we probably want to include given how many users have multiple mods in a single project tree and want to manage them all in the same repo 👍
MythicManiac
changed the title
Local dependencies for projects
Monorepo support for building & publishing multiple projects from a single repo
Jun 13, 2022
Projects should be able to specify other project files as dependencies. This would greatly simplify some cases where packages need several subpackages that should be uploaded but are part of the same project eg a in-house/in-repo dependency or metapackages (like R2API is becoming).
When publishing, dependencies should be published before their dependents if the version number that exists in the repository is lower than the one that exists locally.
The text was updated successfully, but these errors were encountered: