VSCode IntelliSense does not work if the configuration file is outside of the root directory

[jozefmery]

UnoCSS version

v0.55.2

Describe the bug

Placing the UnoCSS configuration file outside of the project root directory breaks the VSCode IntelliSense. Based on the extension's output, it seems that the extension correctly finds and loads the configuration. Also, I'm using the CLI for generation and it seems to work correctly.

Reproduction

1. Move the UnoCSS configuration file from the project root /unocss.config.ts into a sub-directory, e.g., /foo/bar/unocss.config.ts
2. Point the extension to the configuration file by adding the following line in your VSCode settings.json: "unocss.root": "foo/bar"
3. Reload the editor (Close & Open VSCode, or F1 > Developer: Reload Window, or F1 > UnoCSS: Reload UnoCSS)
4. The IntelliSense should be broken

System Info

No response

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[harrytran998]

Same problem with me!

Do like the docs said (https://unocss.dev/integrations/vscode#config) - but no luck 😆. Hope team can fix this!

[darkyelox]

This happens to me too, the settings.json configuration seems to be recognized but the intellisense is not working until I move my config file to root and removed the settings.json property :/ this is a problem for monorepos

[Simon-He95]

I think this issue could be closed