VS Code variable renaming doesn't work in *new* workspaces when Deno plugin is enabled

Describe the bug VS Code’s F2/Ctrl+Shift+R rename for variables doesn’t work in new workspaces when the Deno plugin is enabled. It works fine in TypeScript projects where I haven’t enabled the Deno plugin.

To Reproduce

1. Create a new folder and open it in VS Code
2. Initialize the Deno plugin for the workspace
3. Create a new TypeScript file
4. Type some code, e.g. const tmp = 5;
5. Put the cursor on tmp
6. Hit F2 (or use Refactor -> rename from the right-click context menu)
7. Type in the new name

Expected behavior The variable and all occurrences of the variable are renamed (this is what happens in projects where the Deno plugin hasn’t been enabled).

Actual behavior Nothing happens.

Screenshots I can provide them, if needed.

Versions Deno plugin version: v3.9.2

VS Code versions:

Version: 1.63.2 (system setup) Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3 Date: 2021-12-15T09:40:02.816Z Electron: 13.5.2 Chromium: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.19042

[chmac]

I’m experiencing similar issues. When I export a const from one file, renaming in that file wouldn’t work, but renaming from another file did successfully rename all instances, and after having done that, renaming in the original file now works. I also tried enabling / disabling the settings @jdelarubia shared above, can’t say if this had an impact. Seems like an intermittent bug which will likely be hard to track down.

[jaredkrinke]

@outloudvi figured out that this happens when you open a new workspace and initialize it for Deno the first time. Updated title and steps to reflect this.