Support config auto detection with enabled paths

[kitsonk]

Slightly related:
I have a config like so

{
    "deno.enable": true,
    "deno.unstable": true,
    "deno.enablePaths": [
        "./api",
        "./webapp"
    ]
}

and configs in ./api/deno.jsonc and ./webapp/deno.jsonc. However, VS code doesn't seem to take the config into account, especially the import_map option, despite those folders being listed as "paths". I would expect each path to be considered its own Deno app with potentially a config of its own.

See Monorepo discussion: denoland/deno#9126 (comment)

Originally posted by @eric-burel in #701 (comment)

[kitsonk]

There are two issues here, one is "easy" the other is "hard":

1. When there is an enabled path, check there for config file auto detection versus the root of the workspace. (easy)
2. Support multiple config files in the same workspace. (hard) This is due to that there is only one instance of the Deno language server running, and that instance has a configuration. We don't currently have the infrastructure to support multiple configurations in a single running language server and would be a fairly major re-architecture of how that works. Desired, but diffcult.

[eric-burel]

Thanks for opening a specific issue for this! So until this can be supported, I'll try to investigate how far I can go with just 1 config and import_map. After all, having just one file to manage is also a plus so it's worth it. I'll post updates on the "monorepo discussion" since this repo is specific to the VS Code extension: denoland/deno#9126 (reply in thread)

[Leokuma]

@bartlomieju This is fixed now. I just tested on Deno 1.35.0 and VSCode 1.80.0.

[niedzielski]

This doesn't seem to work for me on Deno v1.35.1, Deno VSCode extension v3.19.1, VSCodium v1.80.1. I have a pretty simple reproduction case here with this structure:

├── deno.json <-- I only know how to resolve std
├── root.test.ts
└── sub
    ├── deno.json <-- I know how to resolve esbuild_deno_loader
    └── sub.ts <-- I import esbuild_deno_loader

deno run sub/sub.ts runs in the CLI but opening sub.ts in VSCode shows typing errors for esbuild_deno_loader. I have the same issue with .ts files as with extensionless executable scripts. The root deno.json is always used but that doesn't have the same import map as the deno.json in the subdirectory.

[nayeemrmn]

Closing in favour of #787.