"Updating imports" happens unnecessarily

Describe the bug I work on a project containing different types of files (mostly *.ts, *.sql, *.svelte, *.json, *.yml, *.md). I observe the following two issues:

1. Whenever I rename a file, even a .sql file for instance, the Svelte plugin tries to update imports in *.svelte files.
2. A Node.js process is forked to update imports and that runs at 100% CPU (or more). I often have to kill the process, it doesn’t stop on its own.

I have about 2000 files in the project and only 100 of them are *.svelte files.

To Reproduce

1. Clone the template project https://github.com/sveltejs/template
2. Open it in VSCode. Ensure you have the Svelte for VSCode plugin installed.
3. Add a file in the src/ directory of any type, try with foo.yml.
4. Rename the file (e.g. to bar.yml). Keep an eye on the info/status toolbar at the bottom of VS Code, you’ll see “Updating imports” quickly show and then disappear.

Expected behavior

1. That renaming a non-svelte (or ts or js) file should not trigger updating of imports in svelte files.
2. That renaming a file that’s not used anywhere does not trigger updating of imports (it’s not imported yet)
3. That imports are not automatically updated, rather, I’m asked if I’d like to update imports. This is the current behaviour in VSCode itself.
4. Ideally, I get to configure which file types should trigger updating of imports in svelte files.

Screenshots N/A

System (please complete the following information):

• OS: Ubuntu Linux 20.04
• IDE: VSCode v1.50.1
• Plugin/Package: Svelte for VSCode v102.3.0

Additional context N/A

[dummdidumm]

This will now only search for imports to update when .ts, .js, .svelte or .json file paths are changed. What’s left to do is the “update imports?”-question.

[joelmukuthu]

Great, thanks for the pointer @dummdidumm!