-
-
Notifications
You must be signed in to change notification settings - Fork 190
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
eth-json-rpc-provider
migration - B1: Remove redundant files and directories.
#1764
Conversation
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: @metamask/[email protected], @types/[email protected], [email protected], [email protected], [email protected] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense!
df4b7dc
to
6d9e07d
Compare
…on-rpc-provider" (#1790) ## Explanation - The contents of `merged-packages/` shouldn't be altered, as it's a temporary directory used for migrating packages into the monorepo. - Any dependency updates for the migration target package need to be handled manually. The migration process involves aligning dependency versions with the monorepo (which may not use the latest version), removing dependencies that are defined in the monorepo root, and removing the `yarn.lock` file from the migration target subpackage. ## Reference - Blocks #1764 - See #1079 (comment) for context on the role of `merged-packages/`.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
…on-rpc-provider" (#1790) ## Explanation - The contents of `merged-packages/` shouldn't be altered, as it's a temporary directory used for migrating packages into the monorepo. - Any dependency updates for the migration target package need to be handled manually. The migration process involves aligning dependency versions with the monorepo (which may not use the latest version), removing dependencies that are defined in the monorepo root, and removing the `yarn.lock` file from the migration target subpackage. ## Reference - Blocks #1764 - See #1079 (comment) for context on the role of `merged-packages/`.
…rectories. (#1764) ## Explanation This PR implements the following incremental step in the process for migrating `eth-json-rpc-provider` into the core monorepo: *** ### Phase B: Staging in `migrated-packages/` #### 1. Remove files and directories that will be replaced by corresponding files in the monorepo root. - [x] **Remove**: `.github/`, `.git*`, `scripts/`, `.depcheckrc.json`, `.yarn/`, `.yarnrc.yml`, `yarn.lock`, `.editorconfig`, `.eslint*`, `.prettier*`, `.nvm*`. - [x] **Keep**: `src/`, `tests/`, `CHANGELOG.md`, `LICENSE`, `package.json`, `README.md`, `jest.config.js`, `tsconfig*.json`, `typedoc.json`. *** See #1551 (comment) for an outline of the entire process. ## Blocked by - [x] #1790 ## References - Contributes to #1685 - Contributes to #1551 ## Changelog N/A ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've highlighted breaking changes using the "BREAKING" category above as appropriate
…on-rpc-provider" (#1790) ## Explanation - The contents of `merged-packages/` shouldn't be altered, as it's a temporary directory used for migrating packages into the monorepo. - Any dependency updates for the migration target package need to be handled manually. The migration process involves aligning dependency versions with the monorepo (which may not use the latest version), removing dependencies that are defined in the monorepo root, and removing the `yarn.lock` file from the migration target subpackage. ## Reference - Blocks #1764 - See #1079 (comment) for context on the role of `merged-packages/`.
…rectories. (#1764) ## Explanation This PR implements the following incremental step in the process for migrating `eth-json-rpc-provider` into the core monorepo: *** ### Phase B: Staging in `migrated-packages/` #### 1. Remove files and directories that will be replaced by corresponding files in the monorepo root. - [x] **Remove**: `.github/`, `.git*`, `scripts/`, `.depcheckrc.json`, `.yarn/`, `.yarnrc.yml`, `yarn.lock`, `.editorconfig`, `.eslint*`, `.prettier*`, `.nvm*`. - [x] **Keep**: `src/`, `tests/`, `CHANGELOG.md`, `LICENSE`, `package.json`, `README.md`, `jest.config.js`, `tsconfig*.json`, `typedoc.json`. *** See #1551 (comment) for an outline of the entire process. ## Blocked by - [x] #1790 ## References - Contributes to #1685 - Contributes to #1551 ## Changelog N/A ## Checklist - [x] I've updated the test suite for new or updated code as appropriate - [x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [x] I've highlighted breaking changes using the "BREAKING" category above as appropriate
Explanation
This PR implements the following incremental step in the process for migrating
eth-json-rpc-provider
into the core monorepo:Phase B: Staging in
migrated-packages/
1. Remove files and directories that will be replaced by corresponding files in the monorepo root.
.github/
,.git*
,scripts/
,.depcheckrc.json
,.yarn/
,.yarnrc.yml
,yarn.lock
,.editorconfig
,.eslint*
,.prettier*
,.nvm*
.src/
,tests/
,CHANGELOG.md
,LICENSE
,package.json
,README.md
,jest.config.js
,tsconfig*.json
,typedoc.json
.See #1551 (comment) for an outline of the entire process.
Blocked by
References
@metamask/eth-json-rpc-provider
to core monorepo #1685eth-json-rpc-provider
into core monorepo #1551Changelog
N/A
Checklist