Handle packageManager in package.json

[viraptor]

When using mise in a project with packageManager defined in package.json, I would expect that package to be installed/used in the same way .foo-version files are used.

But this:

{
  "name": "foo",
  "version": "1.2.3",
  "packageManager": "[email protected]"
}

and

mise x yarn -- yarn

ignores the configured version and runs (for example) v4.x.x

[jdx]

related: #1863

I think this could be done as a vfox/asdf/core plugin which just uses whatever node is on PATH. That wouldn't use corepack but I'm wondering if that ultimately matters to the user.

[viraptor]

Isn't the node choice already done in the yarn plugin? I can mise x [email protected] -- yarn install and it does the "right thing" in this case.

The only remaining issue seems to be not selecting the default version through the json file.

[jdx]

that would be a feature request for asdf-yarn

[NullVoxPopuli]

why asdf-yarn? I don't use yarn, but need packageManager support

[jdx]

ok, then asdf-pnpm

[NullVoxPopuli]

ah, no packageManager plugin? each separate package manager has to separately add support?

[jdx]

it would be possible for someone to make one that installs whichever one is needed but I don't think it's necessary

[jguddas]

I havepnpm = "latest" in my ~/.config/mise/config.toml, to use the version of pnpm specified in the packageManager field
I have added this to the mise.toml that is located besides the package.json:

[hooks]
postinstall = "corepack enable"

[settings]
disable_tools = ["pnpm"]

And that works pretty well, now the shimming of pnpm is done by corepack, but only for this project, everything else still uses mise.