-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple chunks emit assets to the same filename #6071
Comments
Yeah - I am seeing something similar, thanks for reproducing it! My setup uses a yarn workspace and I am linking to app extensions that are not published on NPM either. Running
|
I was looking at the initial ticket just yesterday :) Sorry it takes so long, but a lot on the plate at the moment. It will get fixed, just hang in there for a bit longer. Before I look at the reproduction repo, some info: the chunk names are generated based on their content. So, do you have duplicates? |
@bmansfie I looked at the tar.gz, but seems incomplete. I get missing authModule on it.
|
don't run yarn @rstoenescu |
@nothingismagick that can't change anything. Imported files are still missing (authModule/boot, authModule/routes)... :| |
just unzip and place in node_modules |
Are you two working together? |
No, but I am facing a similar situation and I was able to replicate with his repo. Would love to have this sorted. |
Fix will be available in "@quasar/app" v1.5.0. |
@bmansfie thanks for supplying a reproducible case |
Excellent :) |
Nobody seems to be looking at the other issue that was previous closed due to lack of reproducibility, so I'm opening this new one to make sure it gets looked at.
This error occurs during the production build step.
ERROR in chunk 8daa19ae
js/8daa19ae.8a00ee1b.js
Conflict: Multiple chunks emit assets to the same filename js/8daa19ae.8a00ee1b.js (chunks 8daa19ae and 8daa19ae)
app:build [FAIL] Build failed with errors. Check log above. +0ms
I prepared a smallish project with the build issue. The packages are part of the issue so this has the dependencies included. I'm using a private package that seems to be at the heart of the issue and you can't just install that with npm/yarn so I've bundled it all up here.
https://www.sharpsoftware.dev/dl/quasar/buildIssueDebug.tar.gz
Extract and try to build and it should produce the above error.
The text was updated successfully, but these errors were encountered: