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

Question error [ERROR] Two output files share the same path but have different contents #3763

Closed
ips219 opened this issue May 12, 2024 · 3 comments

Comments

@ips219
Copy link

ips219 commented May 12, 2024

I am trying to upgrade to Angular 17 with Native Federation which is using esbuild, and I'm having an issue building the application with esbuild.

Attached the console.log with the "[ERROR] Two output files share the same path but have different contents" error
error.txt

VRB! at failureErrorWithLog (C:\data\repositorios\AUBAY\aubay-gestion\aubay-gestion-web\mfe-aubay-gestion\node_modules\.pnpm\esbuild@0.19.12\node_modules\esbuild\lib\main.js:1651:15) VRB! at C:\data\repositorios\AUBAY\aubay-gestion\aubay-gestion-web\mfe-aubay-gestion\node_modules\.pnpm\esbuild@0.19.12\node_modules\esbuild\lib\main.js:1059:25 VRB! at C:\data\repositorios\AUBAY\aubay-gestion\aubay-gestion-web\mfe-aubay-gestion\node_modules\.pnpm\esbuild@0.19.12\node_modules\esbuild\lib\main.js:1527:9 VRB! at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

According to the exception thrown, it seems that there is some kind of issue with fullcalendar library.
image

May anybody clarify me if the exception means a compatibility issue of fullcalendar modules with esbuild or address me how can I debug this issue?

Thanks and Best regards.

@evanw
Copy link
Owner

evanw commented May 12, 2024

Some thoughts:

  • Angular adds a lot of custom tooling around esbuild, so this is probably a better question for Angular instead of esbuild
  • You didn't follow the issue reporting instructions (there is no way to reproduce your issue) so I can't help you

Marking this report as unactionable because the issue reporting instructions weren't followed.

@ips219
Copy link
Author

ips219 commented May 13, 2024

Thank you for your support Evan, I'll do as you said.

I thought that given the specific of the error that it may be the expected behaviour for some incompatible conditions.

BR

@evanw
Copy link
Owner

evanw commented Jun 8, 2024

Closing this issue as it has been unactionable without a follow-up reply.

@evanw evanw closed this as not planned Won't fix, can't repro, duplicate, stale Jun 8, 2024
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

2 participants