Should we manage supporting deps?

[Attempt3035]

Many VScode extensions also depend on other tools along with their own binary, like Java or Node. If a user has installed these deps with mise, it often makes sense to use the same local version used by the project, otherwise globally resolved versions differ between developers potentially leading to hard to reproduce bugs in VSCode extensions. Personally, I have settings like:

{
    "mise.customFolderExtensions": [
        {
            "extensionId": "SonarSource.sonarlint-vscode",
            "toolSources": [
                "java"
            ],
            "vscodeSetting": {
                "key": "sonarlint.ls.javaHome"
            },
            "folderName": "java"
        }
    ],
    "mise.customBinaryExtensions": [
        {
            "extensionId": "SonarSource.sonarlint-vscode",
            "toolSources": [
                "node"
            ],
            "supportsShims": true,
            "supportsSymlinks": true,
            "vscodeSetting": {
                "key": "sonarlint.pathToNodeExecutable"
            },
            "binName": "node"
        },
        {
            "extensionId": "oxc.oxc-vscode",
            "toolSources": [
                "node"
            ],
            "supportsShims": true,
            "supportsSymlinks": true,
            "vscodeSetting": {
                "key": "oxc.path.node"
            },
            "binName": "node"
        },
        {
            "extensionId": "Pkl.pkl-vscode",
            "toolSources": [
                "java"
            ],
            "supportsShims": true,
            "supportsSymlinks": true,
            "vscodeSetting": {
                "key": "pkl.lsp.java.path"
            },
            "binName": "java"
        }
    ]
}

Are these settings we should also be adding for supported plugins? I can't see how it would hurt as they will only enable if that mise tool is installed, and with global tool resolution enabled it'll use the global version anyway. Although maybe some users may be confused why one project's plugin might use Node from brew while another might use mise installed node, etc.

Thoughts?

[hverlin]

With which extensions are you facing this issue currently?

[Attempt3035]

Pkl.pkl-vscode would be the main one as it requires external java to operate and the system wide version at least on mine wasn't high enough to run it. Sonarlint in my experience also occasionally has lsp bugs & crashes with a JVM that's too old. OXC is mainly so that the dev machines & ci linking use the same node version for oxfmt etc. Also we run pkl & oxfmt via HK for linting before commit which obv runs on cli, meaning if you don't have these settings, running the tool in cli in vscode uses a different node/java to what the extension doing the same lints does 😩

Not sure what others would prefer to be default in this situation, but I imagine it's reasonable to assume if you've added node, Java etc to your Mise developer tools that all your vscode plugins that have binaries installed via Mise would also use node/JVM deps from Mise as well?

[hverlin]

I agree, users can still disable and fallback to a more granular approach if needed.

The only thing that should take over the mise tools is if you have some node modules (like for biome or oxc) as I think the version in the node modules should take precedence. Usually, the extensions will try to use that one first.

My hope is that once mise is popular enough, every extension add some support for resolving mise natively though.