generated from MetaMask/metamask-module-template
-
Notifications
You must be signed in to change notification settings - Fork 5
Open
Description
The current daemon commands use yarn as an assumed-available PATH entry. We should provide an installer to put ocap-kernel (or ok) on the PATH, pointing to the @ocap/cli. Can we make npm install @metamask/ocap-kernel do this? Is that... a bad idea? Maybe we should prefer npm install @metamask/ocap-kernel-cli or npx -p @metamask/ocap-kernel-cli -- -d ~/.ocap-kernel/
Note: edit freely
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels