Cameron Steffen

I may be grasping at straws here, but the readme and blog post seem to leave a grey area for adding suggestions. The spirit of the policy seems to be...

*facepalm* I'm sorry, I had the changes locally but didn't actually push them up.

> would require adding a type to the declaration of the Option local variable in order to be able to use get_or_insert_default with it My personal take on that scenario...

I think it's good that `[env]` has the single purpose of setting environment variables. It's analogous to a `.env` file.

If you need complex matching logic, then you can collapse those cases into one `mockImplementation` and do it manually. Relying on "specificity" between multiple mocks is too implicit IMO, and...

I think it would be simpler if the setting value is a separate argument instead of using `=`? This is how `git config` works. - `mise settings set x value`

Sorry I meant `mise settings x value`. Would that work?

How about `mise unuse` and deprecate `mise rm|remove`? It's also surprising that "remove" doesn't have a complimenting "add".

Looks like dayjs used to behave this way but was "fixed" in #586.

It seems like this package should be deprecated for Vue 3 users. Take a look at [@vueuse/head](https://github.com/vueuse/head). That is what the latest version of Nuxt [uses](https://nuxt.com/docs/api/composables/use-head).