File id conflict #17041
Unanswered
RussianDragon
asked this question in
Q&A
File id conflict
#17041
Replies: 3 comments 3 replies
-
please provide your configuration, thank you |
Beta Was this translation helpful? Give feedback.
2 replies
-
@alexander-akait @RussianDragon Has this problem been solved? |
Beta Was this translation helpful? Give feedback.
1 reply
-
I had the same error Hotfix was removing |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
Bug report
Only in production mode I have error:
If the current behavior is a bug, please provide the steps to reproduce.
Full history:
I create module federation project. In development mode I not have problem. But turn on production mode I have catch runtime exception. With only specific controller in module.
After day research I found source of the problem. Both project have files in same id.
In shell project:
dist/client/542.2741fd703ebe0b58eb1b.js
In module project:
dist/client/542.4a3b95c1fb4dfe1f29b3.js
Template: [name].[contenthash].js
Filename doesn't matter. Problem in id.
Error in this file
if I change file name, in module project. Example
src\components\widgets\main_menu_widget\main_menu_widget.tsx
->
src\components\widgets\main_menu_widget\main_menu_widget1.tsx
the error disappears. Because file id is - 600. It does not match file in shell project.
What is the expected behavior?
I expect the shell project to have no errors when file ids match in module project
Other relevant information:
webpack version: 5.80.0
webpack-cli version: 5.0.1
Node.js version: v18.16.0
Beta Was this translation helpful? Give feedback.
All reactions