Uncaught (in promise) TypeError: m.createContext is not a function at

Question

Uncaught (in promise) TypeError: m.createContext is not a function at

erkanisuf opened this issue a year ago · 9 comments

I have Vite in Host and Remote is with webpack.
I am getting this error when I build the project:
__federation_shared_…uter-af1a6369.js:20 Uncaught (in promise) TypeError: m.createContext is not a function at __federation_shared_…-af1a6369.js:20:272

I tested with every Vite plugin version its same error.

My config is like this:

     plugins: [react(),
    federation({
      name: "Test",
      remotes: {
        // @ts-ignore
        COMMON: {
          external: 'https://myurl/remoteEntry.js',
          from: 'webpack',
          format:"var",
          externalType: 'url',
        },
      },
      shared: {...deps},
    })
  ]

I cant see remoteEntry.js here in production mode but in dev mode is there.

Answer 1 · 2023-09-18T10:40:57.000Z

getting the same error, though both host and remotes are Vite

Answer 2 · 2023-09-19T00:50:39.000Z

I had a similar issue, and I was able to temporarily work around it by downgrading and specifically setting the version of vite-plugin-federation to the previous version (1.2.3):

"@originjs/vite-plugin-federation": "1.2.3" (no ^ in the version)

Answer 3 · 2023-09-19T10:26:12.000Z

I had a similar issue, and I was able to temporarily work around it by downgrading and specifically setting the version of vite-plugin-federation to the previous version (1.2.3):

"@originjs/vite-plugin-federation": "1.2.3" (no ^ in the version)

I also had the same problem, your advice helped me, thank you.

I would like to note that this error does not depend on whether the module is imported or not. The assembly itself does not start due to the fact that federation() settings have been added to vite.config

Answer 4 · 2023-09-20T06:56:34.000Z

I had a similar issue, and I was able to temporarily work around it by downgrading and specifically setting the version of vite-plugin-federation to the previous version (1.2.3):

"@originjs/vite-plugin-federation": "1.2.3" (no ^ in the version)

For this reason, pnpm only works now in ^1.2.3. (yarn, npm is not working)

Answer 5 · 2023-09-25T20:16:51.000Z

I encountered the same issue with version @originjs/vite-plugin-federation:1.3.1. However, after downgrading to version 1.2.3, the problem was resolved. Thanks @plukconexiom!
I spent a significant amount of time attempting to fix this issue. Given this experience, I am reconsidering the use of this framework for production in a large-scale company setting. I am leaning towards transitioning to single-spa instead.

Answer 6 · 2023-09-28T09:03:42.000Z

Try checking the status of this issue after upgrading to 1.3.2 ,MauriceAyasse submitted PR(#505) to fix the issue

Answer 7 · 2023-09-28T16:32:37.000Z

I won't be confident that the issue is fully fixed as some of the pipeline tests are still failing https://github.com/originjs/vite-plugin-federation/actions/runs/6334057639/job/17203107159 https://github.com/originjs/vite-plugin-federation/actions/runs/6334057639/job/17203107273

Answer 8 · 2023-10-12T13:22:55.000Z

In our project it is still failing with 1.3.2 only 1.2.3 works.
We use those shared libs:

      shared: {
        'react': {},
        'react-dom': {},
        'notistack': {},
        '@emotion/react': {},
        '@emotion/styled': {},
        '@mui/material': {}
      }

Answer 9 · 2023-10-26T21:36:53.000Z

I had the same experience with a material-react-table that needs @emotion/styled, it only works with 1.2.3