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
Currently, all dependencies specified in the Nargo.toml must have a "package"-style Nargo.toml at their root. However, we should also support workspace dependencies.
I've done a prototype at https://github.com/noir-lang/noir/tree/phated/workspace-as-dependencies but it's a breaking change and we need to make sure we are okay with the assumptions: it requires that the dependency name match the name field in the Nargo.toml and we'd need something like a package field to allow the dependency to be aliased (also done in that branch).
Happy Case
A user can depend upon a dependency that has a "workspace"-style Nargo.toml at the root of the project and then they can depend upon individual packages from the workspace.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
Yes
Support Needs
No response
The text was updated successfully, but these errors were encountered:
Problem
Currently, all dependencies specified in the Nargo.toml must have a "package"-style Nargo.toml at their root. However, we should also support workspace dependencies.
I've done a prototype at https://github.com/noir-lang/noir/tree/phated/workspace-as-dependencies but it's a breaking change and we need to make sure we are okay with the assumptions: it requires that the dependency name match the name field in the Nargo.toml and we'd need something like a package field to allow the dependency to be aliased (also done in that branch).
Happy Case
A user can depend upon a dependency that has a "workspace"-style Nargo.toml at the root of the project and then they can depend upon individual packages from the workspace.
Alternatives Considered
No response
Additional Context
No response
Would you like to submit a PR for this Issue?
Yes
Support Needs
No response
The text was updated successfully, but these errors were encountered: