You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When saving invalid JSON to deno.json, an error message is shown (Unable to parse config file JSON...) by VSCode and imports specified in deno.json will no longer work. After saving a valid config the imports remain broken and will show the following error message: Relative import path "supabase-js" not prefixed with / or ./ or ../
I had to restart the language server to get it working again.
We weren't auto-discovering the deno.json in two cases:
1. A project that didn't have a deno.json and just added one.
2. After a syntax error in the deno.json.
This now rediscovers it in both these cases.
Closesdenoland/vscode_deno#867
mmastrac
pushed a commit
to denoland/deno
that referenced
this issue
Jul 26, 2023
We weren't auto-discovering the deno.json in two cases:
1. A project that didn't have a deno.json and just added one.
2. After a syntax error in the deno.json.
This now rediscovers it in both these cases.
Closesdenoland/vscode_deno#867
Describe the bug
When saving invalid JSON to
deno.json
, an error message is shown (Unable to parse config file JSON...
) by VSCode and imports specified indeno.json
will no longer work. After saving a valid config the imports remain broken and will show the following error message:Relative import path "supabase-js" not prefixed with / or ./ or ../
I had to restart the language server to get it working again.
To Reproduce
deno.json
Expected behavior
After saving a valid config the imports should be recognized without having to restart the language server.
Versions
vscode: 1.74.1 deno: 1.34.2 extension: 3.19.1
The text was updated successfully, but these errors were encountered: