UnoCSS version

66.6.0 (LATEST at Feb 25th)

Describe the bug

As #4135 (comment), This issue is a supplement to #4133.

Actually, current VSCode extension doesn't only stops working when meeting unknown path import, but also when meeting any other config parsing / semantic error, like the video below.

Even if according to #4133 (comment), I think there is no reason to stop future context loading after catching an error, which makes users still cannot get IDE support even after they correct the config file unless they reload the whole editor.

(Please ignore what I said in #4135 (comment), I tried locally and found that we still need #4135 to fix it)

Hope it helps, thanks.

Reproduction

System Info

MacOS 26.3 with VSCode 1.107.0

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.