feat(server): invalidate module with hmr

[bluwy]

Description

Fix #6871

New API: server.reloadModule that invalidates a module with hmr, unlike moduleGraph.invalidateModule

Additional context

Question:

1. Would the API name be confusing?
2. Is the first parameter ok? e.g. a string vs a ModuleNode

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the Commit Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[patak-dev]

Would the API name be confusing?

I think that it may be confusing that server.invalidateModule and moduleGraph.invalidateModule has the same name but they have different side effects.

Is the first parameter ok? e.g. a string vs a ModuleNode

We should probably follow the current convention in the module graph and pass a module instead.

What about server.reloadModule(module, ...)? IMO it more clearly states that it will trigger a Hot Module Reload for the module, and not only invalidate it.

[bluwy]

reloadModule sounds nice! I updated to use that.

We should probably follow the current convention in the module graph and pass a module instead.

I also updated to a ModuleNode. I initially didn't went with it since the API would tie to the moduleGraph. And to keep it consistent with ssrLoadModule. But I feel like ModuleNode would be more futureproof too so it might be fine.

[rosskevin]

This PR would make my i18next resources HMR desperately easy (if I have the correct understanding). Invalidating my virtual module should cause all the relative i18next resource to refresh. Aside from this, it looks like a detailed mess (outside of the vite ecosystem) to invalidate old resources and load new.

[patak-dev]

Thanks for your feedback @rosskevin, it's very helpful to know real use cases for PRs 🙏🏼
This feature will be included in Vite 3.2