Embedded Aube for project package management and shared storage

[anthknee]

I’m choosing how to manage global npm CLIs, project tools, and application dependencies while reducing duplicate package storage.

The options I see each have a limitation:

• Embedded Aube for both: mise does not currently expose embedded Aube for project package management.
• Embedded Aube for CLIs, standalone Aube for projects: the two installations use separate stores, and embedded installs disable the global virtual store.
• Standalone Aube for both: storage can be shared, but CLI installations lose mise’s additional npm provenance verification.

Could mise expose its embedded Aube for project package management and shared storage while preserving its security checks and reliable cleanup?

Thanks

[jdx]

Thanks for the detailed write-up. I'm going to say no to this one.

The embedded aube is an implementation detail of the npm backend. Exposing it as a project package manager would make its CLI, store layout and behavior part of mise's public surface. mise is a tool and environment manager, not a package manager for your application dependencies, and I don't want to take on that scope.

If you want one store shared between global CLIs and projects, use standalone aube for both. That gives up mise's extra npm provenance checks on the CLIs. If you need those checks, keep the CLIs on the npm: backend and run projects with standalone aube. The stores stay separate, which is the cost of that split.

AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: claude-code_2-1-317_agent.