-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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 to new controller packages #5270
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
I have read the CLA Document and I hereby sign the CLA |
Marking as |
I have added the token as |
I'm going to keep this PR in draft mode so that if we need to make updates we can continue to access the preview versions of the aforementioned packages via the GitHub Package Registry, but feel free to leave your comments on this PR. |
d874a30
to
a53a1e4
Compare
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
f565e97
to
39f804e
Compare
This comment was marked as resolved.
This comment was marked as resolved.
39f804e
to
bb172c3
Compare
bb172c3
to
faa0eee
Compare
668be34
to
e1675d1
Compare
e1675d1
to
4cb3033
Compare
`@metamask/controllers` is deprecated, and most of the controllers that lived here are now located in their own package ([1]). This commit replaces `@metamask/controllers` in `package.json` with references to these packages and updates `import` lines to match. [1]: MetaMask/core#831
CI now supports fetching packages from the GitHub Packages registry on draft PRs. This is meant to support the use of "preview" builds of controller packages, to more easily test controller changes before they are released.
Co-authored-by: Mark Stacey <[email protected]>
4cb3033
to
1e59d83
Compare
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.
LGTM. The changes are straightforward 👍
…ller-packages * origin/main: [IMPROVEMENT] Remove deeplink warning for SDK and SDK as dependency (#5449) On-Ramp: Settings and Activation Keys (#5455) [FIX] Screenshot deterrent analytics (#5468) On-ramp: Remove unused constants (#5462) On-ramp: Refactor Regions view to componentization (#5413) Approval error when insufficient balance (#5440) remove extra zero balance account potentially created from seeking ahead (#5459) [IMPROVEMENT] Refactor Analytics Events (#5454)
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.
Pass automation. LGTM.
Development & PR Process
release-xx
label to identify the PR slated for a upcoming release (will be used in release discussion)needs-dev-review
label when work is completedneeds-qa
label when dev review is completedQA Passed
label when QA has signed offDescription
@metamask/controllers
is deprecated, and most of the controllers that lived here are now located in their own package. This commit replaces@metamask/controllers
inpackage.json
with references to these packages and updatesimport
lines to match.Issue
Testing notes
This is a behind-the-scenes change, and there should be no changes to existing functionality — everything should work as it does currently. I'm not sure what the best protocol to test these sorts of changes is (maybe run through the most common scenarios?)
Custom registry setup (skip these steps, these were only relevant before we published these packages)
Note that before this PR gets merged, preview versions of the new packages, which live on GitHub Packages, will be used. Without specially configuring NPM, these packages will not be accessible locally, and therefore you will not be able to run
yarn setup
. To get this working:.npmrc
in the root directory with the following content (note: this file is gitignored, so don't worry about it ending up in the repo):Now you should be able to run
yarn setup
, then load the app as you normally would.Checklist