Version: Deno 1.38.5 / Fresh 1.5.1

Steps to recreate:

1. Create a new valid component file, e.g., MyNewComponent.tsx.
2. Start adding that component to your code (not as an import; begin typing the name of the component so that the auto-complete window pops up)
3. When you see your component, hit enter or click it to auto-complete

Result:

VS code only completes the name of the component; it doesn't add it as an import, as it would if you were importing an existing component.

However, VS Code will automatically import the component if you close and re-open the project. Then the import is auto-added to the top of the file, as it should be, and as expected:

This makes me think the auto-completion must not scan continuously for new components, and instead, maybe only scans once at the start of the project. (Or, perhaps, does so at irregular enough intervals that newly created components are not included.)

Ideally, it would be optimal for developer experience to have all files available for auto-import/complete.

[EDIT]: While adding a new component reliably triggers this behavior, I've also encountered it when the component already existed, too. In both cases, closing and reopening the project fixes the issue. But it's odd because in both cases, VS Code still shows the file and the path, and you can still select them; it's just that the import list is not updated in any way.