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
While maintaining Wallet Framework packages, we have found that controller dependencies and type-only dependencies frequently get miscategorized. It would be good to have a resource we can point people to whenever confusion arises.
Acceptance Criteria
A document exists which explains:
Why peerDependencies exists and what it does
Situations in which filing a dependency under devDependencies + peerDependencies is desired over dependencies (e.g. controllers)
Situations in which it is not appropriate to file a dependency under devDependencies + peerDependencies (e.g. type-only dependencies)
When and how to bump peerDependencies in a monorepo
The text was updated successfully, but these errors were encountered:
While maintaining Wallet Framework packages, we have found that controller dependencies and type-only dependencies frequently get miscategorized. It would be good to have a resource we can point people to whenever confusion arises.
Acceptance Criteria
peerDependencies
exists and what it doesdevDependencies
+peerDependencies
is desired overdependencies
(e.g. controllers)devDependencies
+peerDependencies
(e.g. type-only dependencies)peerDependencies
in a monorepoThe text was updated successfully, but these errors were encountered: