Skip to content
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

Closed
bmansfie opened this issue Jan 10, 2020 · 12 comments
Closed

Multiple chunks emit assets to the same filename #6071

bmansfie opened this issue Jan 10, 2020 · 12 comments

Comments

@bmansfie
Copy link

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.

@nothingismagick
Copy link
Contributor

nothingismagick commented Jan 10, 2020

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 quasar build -m ssr with your attached project results in:

ERROR in chunk 8daa19ae
js/8daa19ae.7552df51.js
Conflict: Multiple chunks emit assets to the same filename js/8daa19ae.7552df51.js (chunks 8daa19ae and 8daa19ae)


 app:build [FAIL] Build failed with errors. Check log above

@rstoenescu
Copy link
Member

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?

@rstoenescu
Copy link
Member

@bmansfie I looked at the tar.gz, but seems incomplete. I get missing authModule on it.

ERROR in ./src/boot/auth.js
Module not found: Error: Can't resolve 'authModule/boot' in '/Users/Razvan/Downloads/quasarBuildIssueDebug/src/boot'
 @ ./src/boot/auth.js 1:0-43 2:15-27
 @ ./.quasar/client-entry.js
 @ multi ./.quasar/client-entry.js

ERROR in ./src/router/routes.js
Module not found: Error: Can't resolve 'authModule/routes' in '/Users/Razvan/Downloads/quasarBuildIssueDebug/src/router'
 @ ./src/router/routes.js 3:32-60
 @ ./src/router/index.js
 @ ./.quasar/app.js
 @ ./.quasar/client-entry.js
 @ multi ./.quasar/client-entry.js

@nothingismagick
Copy link
Contributor

don't run yarn @rstoenescu

@rstoenescu
Copy link
Member

@nothingismagick that can't change anything. Imported files are still missing (authModule/boot, authModule/routes)... :|

@nothingismagick
Copy link
Contributor

authModule.zip

@nothingismagick
Copy link
Contributor

just unzip and place in node_modules

@rstoenescu
Copy link
Member

Are you two working together?

@nothingismagick
Copy link
Contributor

No, but I am facing a similar situation and I was able to replicate with his repo. Would love to have this sorted.

@rstoenescu
Copy link
Member

Fix will be available in "@quasar/app" v1.5.0.

@rstoenescu
Copy link
Member

@bmansfie thanks for supplying a reproducible case
@nothingismagick thanks for pointing out the authModule was already in node_modules and no yarn/npm install was necessary

@bmansfie
Copy link
Author

Excellent :)

mesqueeb pushed a commit to mesqueeb/quasar that referenced this issue Feb 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants