fix(css): fix stale css when reloading with hmr disabled (#10270)

[russelldavis]

Description

Fixes #10270.

In the non-hmr code path, when invalidating a module, it wasn't invalidating the importers. This meant that CSS dynamically generated based on a module's contents (e.g., what tailwind does) would not regenerate when refreshing a page.

The HMR code path already invalidated importers, which is why the bug didn't exist with HMR enabled. This change makes the invalidation consistent between HMR and non-HMR.

The changes are quite minimal -- it's just merging some of the logic from the invalidate function (in hmr.ts) into the invalidateModule function (in moduleGraph.ts) and updating the call site.

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 PR Title 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.

[sapphi-red]

Thanks for the PR!

I'm not too sure, but the code looks good to me.
Also I tested this PR with a simple vue project and it worked with both hmr: true and hmr: false.

[patak-dev]

Looks good to me too. Let's merge it in the 4.1 beta next week to be safe.