-
-
Notifications
You must be signed in to change notification settings - Fork 187
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
Migrate @metamask/eth-json-rpc-provider
into core monorepo
#1707
Conversation
The package manifest, README, and PR template have been updated.
* Migrate both provider functions The functions `providerFromEngine` and `providerFromMiddleware` have been migrated from `@metamask/eth-json-rpc-middleware`. The `SafeEventEmitterProvider` is now a class with its own separate module, rather than a type. Hopefully this will help prevent future type errors. The error in the `SafeEventEmitterProvider` type in `@metamask/eth-json-rpc-middleware` has been corrected; the response in in the callback is now optional. Everything should be fully documented and tested. * Export type * Fix spelling mistake Co-authored-by: Alex Donesky <[email protected]> * Improve test names --------- Co-authored-by: Alex Donesky <[email protected]>
Bumps [@metamask/eslint-config-jest](https://github.com/MetaMask/eslint-config) from 11.0.0 to 11.1.0. - [Release notes](https://github.com/MetaMask/eslint-config/releases) - [Commits](MetaMask/eslint-config@v11.0.0...v11.1.0) --- updated-dependencies: - dependency-name: "@metamask/eslint-config-jest" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [@metamask/eslint-config](https://github.com/MetaMask/eslint-config) from 11.0.2 to 11.1.0. - [Release notes](https://github.com/MetaMask/eslint-config/releases) - [Commits](MetaMask/eslint-config@v11.0.2...v11.1.0) --- updated-dependencies: - dependency-name: "@metamask/eslint-config" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Mark Stacey <[email protected]>
Bumps [@metamask/eslint-config-typescript](https://github.com/MetaMask/eslint-config) from 11.0.2 to 11.1.0. - [Release notes](https://github.com/MetaMask/eslint-config/releases) - [Commits](MetaMask/eslint-config@v11.0.2...v11.1.0) --- updated-dependencies: - dependency-name: "@metamask/eslint-config-typescript" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Mark Stacey <[email protected]>
Bumps [@metamask/eslint-config-nodejs](https://github.com/MetaMask/eslint-config) from 11.0.1 to 11.1.0. - [Release notes](https://github.com/MetaMask/eslint-config/releases) - [Commits](MetaMask/eslint-config@v11.0.1...v11.1.0) --- updated-dependencies: - dependency-name: "@metamask/eslint-config-nodejs" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Mark Stacey <[email protected]>
The version has been changed to v0.0.1 so that the first release can be v1. I set this to v1 forgetting that our release automation would also attempt to set this.
* 1.0.0 * Update changelog --------- Co-authored-by: github-actions <[email protected]> Co-authored-by: Mark Stacey <[email protected]>
* deps: @metamask/safe-event-emitter@^2.0.0->^3.0.0 * deps: migrate from json-rpc-engine to @metamask/json-rpc-engine
--------- Co-authored-by: github-actions <[email protected]> Co-authored-by: legobt <[email protected]>
v1.0.1 contains two changes that should have been considered semver-major: - Type-interface incompatability with previous version (MetaMask/json-rpc-engine#139) - Introduced dependency `@metamask/json-rpc-engine` indicates a minimum supported Node.js version of 16. This prevents the module from installing on some package manager configurations, like default yarn classic. This will be re-released as v2.0.0.
Required by update of `@metamask/json-rpc-engine` (#16)
Required by update of `@metamask/json-rpc-engine` (#16)
--------- Co-authored-by: github-actions <[email protected]> Co-authored-by: legobt <[email protected]>
…25) * deps: @metamask/utils@^5.0.1->^8.1.0 * deps: @metamask/json-rpc-engine@^7.0.0->^7.1.0 * deps: @metamask/utils@^7.1.0->^8.1.0
--------- Co-authored-by: github-actions <[email protected]> Co-authored-by: legobt <[email protected]> Co-authored-by: legobeat <[email protected]> Co-authored-by: Maarten Zuidhoorn <[email protected]>
…norepo - added: `eslint-plugin-promise` - removed: `eslint-plugin-node` Closes #1683
f6738df
to
72ae659
Compare
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: @lavamoat/[email protected], @metamask/[email protected], @metamask/[email protected], @metamask/[email protected], @types/[email protected] |
I think this should not be merged before bumping workspace dependencies on the package in line with latest: |
@MajorLift perhaps would be better to break down this PR into multiple ones to make it easier to see and review the changes, and creating the first two PRs on the original repository: |
Thanks for the feedback! I'll be closing this PR and reopening it. @legobeat Thanks for pointing this out. It looks like using the latest version of @mikesposito I just opened the first two PRs on the original repo. It's looking like most of the commits will happen on the last PR after the merging step. |
Explanation
References
~4.6.3
#1682eslint
andprettier
#1683eth-json-rpc-provider
into core monorepo #1551Changelog
Checklist