You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Module federation is working with npm run dev but not with npm run build then npm run start (Container initialization failed as it has already been initialized with a different share scope)
#3474
Open
AmineAyachi opened this issue
Dec 19, 2023
· 2 comments
The text was updated successfully, but these errors were encountered:
AmineAyachi
changed the title
Module federation is working with npm run dev but not with npm run build then npm run start
Module federation is working with npm run dev but not with npm run build then npm run start (Container initialization failed as it has already been initialized with a different share scope)
Dec 19, 2023
Hello i created a new next js application with this configs:
package.json:
tsconfig.json :
next.config.js:
When i run npm run dev , everthing works but when i run npm run build then npm run start i got the application runing but it expose a bad remoteEntry.js file :
here is the file :
https://docs.google.com/document/d/1x5JYZRq-1-Hzx1FXzKLShEGk49NYEJ5Vz7IiWRzowBg/edit?usp=sharing
here is the url i am using for remoteEntry.js :
http://localhost:3000/_next/static/chunks/remoteEntry.js
The text was updated successfully, but these errors were encountered: