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
The current daemon commands use
yarnas an assumed-available PATH entry. We should provide an installer to putocap-kernel(orok) on the PATH, pointing to the@ocap/cli. Can we makenpm install @metamask/ocap-kerneldo this? Is that... a bad idea? Maybe we should prefernpm install @metamask/ocap-kernel-cliornpx -p @metamask/ocap-kernel-cli -- -d ~/.ocap-kernel/Note: edit freely