-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
remove any peerDependencies on packages other than hub-common #655
Comments
NOTE: the above is true of teams in template-js too. Furthermore, the processors package only depends on initiatives for |
This was referenced Sep 30, 2021
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Fortunately it looks like it's just sites that has
peerDependences
on initiatives and teams.That causes:
peerDependencies
up to date manually at release timeProposed solution:
getInitiativeTemplate()
,addInitiative()
,updateInitiativeSiteId()
(and any fns they need) to commonThe text was updated successfully, but these errors were encountered: