HMR didn't work for dynamic imported modules (React)

[Alex-Ferreli]

Describe the bug

Plugin-react-refresh didn't refresh dynamic imported modules.

Reproduction

Repository to reproduce:
https://github.com/Alex-Ferreli/vite-react-hmr-dynamic-import

It's the default react-ts template with a dynamic import of a React component.

System Info

Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:

System:
    OS: Linux 5.8 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz
    Memory: 404.95 MB / 15.43 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 15.5.0 - ~/.nvm/versions/node/v15.5.0/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 7.3.0 - ~/.nvm/versions/node/v15.5.0/bin/npm
  Browsers:
    Chrome: 89.0.4389.90
    Firefox: 86.0.1
  npmPackages:
    vite: ^2.1.3 => 2.1.3

Used package manager: yarn

Logs

The HMR in console print the parent file:
[vite] hot updated: /src/App.tsx

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

• [ x] Read the Contributing Guidelines.
• [ x] Read the docs.
• [ x] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [ x] Provide a description in this issue that describes the bug.
• [ x] 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 https://github.com/vuejs/vue-next instead.
• [ x] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

[davidbonnet]

You confirm that this is a Vite bug and not an upstream one?
IMHO, this issue is not a minor one: it this is a quite common issue for React apps for splitting bundles.

[Shinigami92]

@davidbonnet it's quite arguable what's a minor and what's an upstream bug
This doesn't affect the whole Vite ecosystem but the react ecosystem

We currently only have these two p3-* labels, we may discuss internally if we want another label for each framework 🤔

[Alex-Ferreli]

I have found the solution. I have updated the repository blocking version on package.json to reproduce the solution with the exact version of all packages of the initial issue.

This is the fix:
Alex-Ferreli/vite-react-hmr-dynamic-import@de1957a

Really strange bug, seems that the dynamically imported component must be created and default exported separately.

[davidbonnet]

As I suspected, this an upstream issue located in react-refresh. Might be good to upgrade it to v0.10.0 though.

For now, the issue raised by @Alex-Ferreli is intentional ("Anonymous direct exports […] are currently ignored."):
https://github.com/facebook/react/blob/a817840ea7d3818c0590cccb9159b13220f4fdb4/packages/react-refresh/src/ReactFreshBabelPlugin.js#L430-L440

      ExportDefaultDeclaration(path) {
        const node = path.node;
        const decl = node.declaration;
        const declPath = path.get('declaration');
        if (decl.type !== 'CallExpression') {
          // For now, we only support possible HOC calls here.
          // Named function declarations are handled in FunctionDeclaration.
          // Anonymous direct exports like export default function() {}
          // are currently ignored.
          return;
        }

Ironically, something like:

function identity(value) {
  return value;
}

export default identity(() => {
  return <div>TRY TO CHANGE ME</div>;
});

…would work. It is however considered as bad practice to export unnamed components.

The issue I witnessed is slightly different, and still located in react-refresh (facebook/react#21179).

IMHO, we can close this and re-open a new issue to upgrade the dependency once these are fixed.

[patak-dev]

Thanks for digging into this @davidbonnet, I think we can leave this one open with the bug: upstream label. Let's update the dependency and close it when there is a release

[davidbonnet]

Opened facebook/react#21181 to that effect.

[Alex-Ferreli]

Thanks @davidbonnet for the clarification.

Maybe it's better to write it on the documentation, because this is the first time that i found and use this workaround, it's not specified anywhere.

[davidbonnet]

IMHO, it should at least refresh the page. I didn't have time yet to investigate the origin of that issue:
facebook/react#21181 (comment).

[xiaomuzizier]

I have same issue

[xiaomuzizier]

please see it. Have I same issue with you?