In one of the latest PRs a new dependency was introduced for the package networks for @hethers/providers, which caused errors to be thrown during npm run build-all in a fresh installation, since the dependency is not specified in packages/networks/package.json. But if it is added there, that introduces circular dependencies between packags, which also breaks the build process. So the only solution is to remove the providers dependency from networks.
In one of the latest PRs a new dependency was introduced for the package
networksfor@hethers/providers, which caused errors to be thrown duringnpm run build-allin a fresh installation, since the dependency is not specified inpackages/networks/package.json. But if it is added there, that introduces circular dependencies between packags, which also breaks the build process. So the only solution is to remove theprovidersdependency fromnetworks.Related issue(s):
Fixes #
Notes for reviewer:
Checklist