Any way to use currently selected sdk in project that requires another version of it

[ZuBB]

Disclaimer: I am not sure if this is a known issue or a feature request, or a bug, so general Q it is

I mostly used Nodejs, so my experience is almost entirely related to it. Let's say my global version is v20, and in some projects via .node-version, v18 is recommended/required. So when I try to run npm run build (for example), I might see some complaints/warns, but at least the command will be invoked. And there is a big change that all will be totally OK. This is true for nvm and fnm managers that I used for a long time. With "mise", this is no longer a case. Even if there are no packages in the dependency tree with binding to the native package, this will not work. mise just wants to install the required version; no other options are possible.

Any thoughts on this?

[jdx]

I'm not following. Can you maybe show some example workflows of the expected and current behavior to make it clearer?

[ZuBB]

I am saying that some old projects have .node-version/.nvmrc but don't have .mise.toml. And if I follow the advice of the author, then I will not be able to leverage the presence of those files

[booniepepper]

Also just want to say that I am really trying to follow this, but the language here is not precise enough to know how to replicate the behavior you don't want. I've been writing JS since the 90s (remember MooTools?) and seen all sorts of tooling and libraries come and go, but I still don't feel qualified to guess what you want or whether it's going to be compatible with the goals of Mise

[ZuBB]

I might be not the best explainer, but the output from terminal (at the top) can't be read in multiple ways.

[booniepepper]

Wait what are we talking about? I thought this was a discussion about controlling versions of nodejs?

[ZuBB]

It's about ability to use currently/globally selected version ask in project that have nvmrc/node-version files with other version

[rakuyoMo]

I have an idea:

when the dependency version required by the project does not exist, but there are other versions (whether global or otherwise), use interactive questioning to ask the user whether to use other versions (maybe higher than the project requirements, or maybe Below, I think it's possible to provide a list for the user to choose from).

For example, the project requires node@18, but the user did not install it. The user installed node@17 and node@20. At this time, a list containing these two versions can be provided for users to choose which one to use.

As for possible subsequent command execution errors, I think that should be a problem that the user needs to solve.

Further, it is possible to add a configuration in .mise.toml: disallow selection of versions other than the specified version. (This depends on what the default behavior is. You can also set the default behavior to "Do not allow selection" and then manually open a new interactive question)