refactor: Prepare for publishing packages to npm #507
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Rename and reconfigure: - @ocap/kernel -> @MetaMask/ocap-kernel - @ocap/store -> @metamask/kernel-store - @ocap/utils -> @metamask/kernel-utils
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To publish our packages to
npm, we need to scope them under the@metamask/*organization. Packages that are to remain private (for now or in perpetuity) can remain scoped under@ocap/*. Packages that need to be published includes everything that we'll want to use in production. Consequently, we rename and reconfigure the following:@ocap/kernel->@metamask/ocap-kernel@ocap/store->@metamask/kernel-store@ocap/utils->@metamask/kernel-utils@ocap/shims->@metamask/kernel-shims@ocap/rpc-methods->@metamask/kernel-rpc-methods@ocap/errors->@metamask/kernel-errors@ocap/logger->@metamask/logger@ocap/streams->@metamask/streamsSince we're only likely to use the CLI for internal purposes for the time being, we keep it private for now. The extension and Node.js runtimes are not likely to ever be published as libraries, and can also remain private.