How to make sure that .vscode/settings.json is loaded?

[JayanAXHF]

Checked other resources

• This is not a bug report or feature request (Please use issues for those).
• This is a question about rustaceanvim, not rust-analyzer or Neovim.
• This is not a question about autocompletion.
• I have read the README.
• I have read the FAQ.
• I have searched for a solution using :h rustaceanvim.
• I have searched existing discussions.
• I have searched the existing issues/discussions of other plugins related to this question (if applicable).
• I have searched the existing rust-analyzer discussions (if applicable).
• I have added a very descriptive title to this question.

Description

Hi, I've been using rustaceanvim for quite some time, and haven't run into major challenges. However, I recently started working on a very large workspace (rustc), and since then my entire LSP config has been acting up. As such, I wanted rustaceanvim to load a .vscode/settings.json file to load the appropriate settings for the workspace, but I am afraid that it hasn't loaded them, not correctly at least. If there a way I can check if the settings were loaded (correctly) or not?

Example Code

{
    "git.detectSubmodulesLimit": 20,
    "rust-analyzer.linkedProjects": [
        "Cargo.toml",
        "compiler/rustc_codegen_cranelift/Cargo.toml",
        "compiler/rustc_codegen_gcc/Cargo.toml",
        "library/Cargo.toml",
        "src/bootstrap/Cargo.toml",
        "src/tools/rust-analyzer/Cargo.toml"
    ],
    "rust-analyzer.check.invocationStrategy": "once",
    "rust-analyzer.check.overrideCommand": [
        "python3",
        "x.py",
        "check",
        "--json-output",
    ],
    "rust-analyzer.rustfmt.overrideCommand": [
        "/Users/jayansunil/Dev/rust/rustc/build/host/rustfmt/bin/rustfmt",
        "--edition=2024"
    ],
    "rust-analyzer.procMacro.server": "/Users/jayansunil/Dev/rust/rustc/build/host/stage0/libexec/rust-analyzer-proc-macro-srv",
    "rust-analyzer.procMacro.enable": true,
    "rust-analyzer.rustc.source": "./Cargo.toml",
    "rust-analyzer.cargo.sysrootSrc": "./library",
    "rust-analyzer.cargo.extraEnv": {
        "RUSTC_BOOTSTRAP": "1"
    },
    "rust-analyzer.cargo.buildScripts.enable": true,
    "rust-analyzer.cargo.buildScripts.invocationStrategy": "once",
    "rust-analyzer.cargo.buildScripts.overrideCommand": [
        "python3",
        "x.py",
        "check",
        "--json-output",
        "--compile-time-deps",
    ],
    "rust-analyzer.server.extraEnv": {
        "RUSTUP_TOOLCHAIN": "nightly"
    },
    "files.associations": {
        "*.fixed": "rust",
        "*.pp": "rust",
        "*.mir": "rust"
    }
}

Neovim version (nvim -v)

v0.11.2

Operating system/version

macOS 15.2

Output of :checkhealth rustaceanvim

==============================================================================
rustaceanvim:                                                             1 ⚠️

Checking for Lua dependencies ~
- ✅ OK [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap) installed.

Checking external dependencies ~
- ⚠️ WARNING No debug adapter detected. Make sure either lldb or codelldb is available on the path.
- ✅ OK rust-analyzer: found rust-analyzer 1.89.0 (29483883 2025-08-04)
- ✅ OK Cargo: found cargo 1.89.0 (c24e10642 2025-06-23)
- ✅ OK rustc: found rustc 1.89.0 (29483883e 2025-08-04)

Checking config ~
- ✅ OK No errors found in config.

Checking for conflicting plugins ~
- ✅ OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- ✅ OK tree-sitter parser for Rust detected.

[mrcjkb]

Hey 👋

I will be removing .vscode/settings.json support from rustaceanvim soon. I recommend you use codesettings.nvim for that, as it supports multiple language servers.

• feat(lsp)!: remove .vscode/settings.json support in favour of codesettings.nvim #938 (comment)

While rustaceanvim still supports it, keep in mind that neovim doesn't support JSON5.

[JayanAXHF]

Thanks for the swift reply! One question, whats the latest version of rustaceanvim with codesettings.nvim support?

[mrcjkb]

There's a bug in versions prior to rustaceanvim 7.0.9 that requires extra configuration in codesettings.nvim.
Since rustaceanvim 7.0.9, it works out of the box (you just need to follow the codesettings.nvim instructions to set it up).

[JayanAXHF]

Alright, Thanks

…

On Thu, 8 Jan 2026 at 18:04, Marc Jakobi ***@***.***> wrote: There's a bug in versions prior to rustaceanvim 7.0.9 that requires extra configuration in codesettings.nvim. Since rustaceanvim 7.0.9, it works out of the box (you just need to follow the codesettings.nvim instructions to set it up). — Reply to this email directly, view it on GitHub <#941 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARUQWK65XXU2VJMRCX7LL2D4FZFD5AVCNFSM6AAAAACRBUQ7ROVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKNBUGQ2DMMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>