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
{{ message }}
This repository has been archived by the owner on Jan 27, 2020. It is now read-only.
I've noticed that often new UI components have added a new npm dependency.
While I think it's important to be flexible, this is not sustainable.
We should have some way to separate the dependencies of UI components from the dapp itself, and possibly have a separate process for developers requesting to add a dependency.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I've noticed that often new UI components have added a new npm dependency.
While I think it's important to be flexible, this is not sustainable.
We should have some way to separate the dependencies of UI components from the dapp itself, and possibly have a separate process for developers requesting to add a dependency.
The text was updated successfully, but these errors were encountered: