Module graph doesn't track new files that were previously missing

[bluwy]

Describe the bug

When File A imports a non-existent File B like import { foo } from './file_b', and later we create file_b.js to fix it, Vite doesn't pick up this new change and reload the page.

Note:

• Happens in both client and SSR.

Workaround:

• Client: Refresh the page.
• Server: Update File A with a fake change and Ctrl+S. (because of ssrError cache in the module graph)

Potential fix:

• Keep a shell module if an import doesn't exist so we have a direct link to the non-existent file upon creation.
• OR when a new file is created, update all modules that are in an error state.

Reproduction

https://stackblitz.com/edit/vitejs-vite-biac4m?file=_foo.js,main.js&terminal=dev

Steps to reproduce

main.js imports _foobar which doesn't exist.

1. Rename _foo.js to _foobar.js to fix it.
2. Notice that the page doesn't reload.

System Info

Stackblitz

Used Package Manager

npm

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[tuchg]

related #10602