auto-imports (import suggestions) randomly stopped working about vscode HOT 1 OPEN

Today was one of the days where this actually booted up correctly, so I think I have some more info that might help debug this!

I started my computer normally and it definitely chalks up to a timing issue somewhere, I'm thinking between docker and wsl and vscode working together. My startup process is always the same steps:

1. open a terminal
2. do wsl shutdown to make sure there isn't some lingering process
3. start docker desktop (which has the wsl integration and such)
4. start vscode

The times where this seems to work, I've noticed a couple things happen:

• my terminal pnpm commands seem to map into the docker instance from vscode. So instead of having to do something like a pnpm install inside docker, the pnpm install automatically scopes to docker
• my husky commands that need to run inside docker work just fine in the vscode source control panel when doing a commit
• all the imports and such that are an issue in the description work correctly

When it doesn't work, the above all fail and I have to manually run all commands in a docker context. So it seems like there's some timing issue where vscode doesn't initialize the order between wsl, docker, and other vscode setups in the correct order every time. This then seems to cause something like the typescript imports to fail with aliasing issues or something (given the error log shown above).

Is there some way to a) see the initialization flow for the entirety of vscode as a whole, and b) force it to always initialize in the same correct order each time?

EDIT: I might be mistaken on the above comment, but it seems related. After working through today, I had some lulls between meetings where I wasn't actively touching vscode at all for an hour or so at a time. And...now we're back to all the import stuff broken again. So just not touching it at all just broke it 😞

from vscode.