fix: don't invalidate when code is invalid

[sapphi-red]

Description

import.meta.hot.accept(mod => {
  // mod is undefined when the code contains invalid syntax
  if (isReactRefreshBoundary(mod)) { // isReactRefreshBoundary(undefined) returns false
    ${timeout}
  } else {
    import.meta.hot.invalidate(); // this invalidate is called
  }
}

This PR adds if (!mod) return to fix invalidate happening.

This fixes vitejs/vite#11365.

Additional context

---

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.

[ArnaudBarre]

I have the same condition in react-swc plugin 👍

[EduardoLopes]

any date for next release with this fix?

[SamuelScheit]

@patak-dev we are also facing the same issue and waiting for a release, as manually installing this package from github doesn't work with a monorepo.

[Intevel]

Same here, would be great to see this released soon.

[ArnaudBarre]

Available in 3.0.1!

[Intevel]

Thank you @ArnaudBarre

[SamuelScheit]

I still have the same issue vitejs/vite#11365 that vite gets stuck in an invalidating loop.
I've found a workaround by always using the isReactRefreshBoundary timeout function and commenting out import.meta.hot.invalidate().

[ArnaudBarre]

I will check if it's still happening with #79

My advice is to stop doing barrels imports. Took me some hours when migrating from CRA, but that was worth it. Imports are not as beautiful, but with time you learn to don't care and IDE renaming/find usages & HMR works a lot better