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

File casing produces error on Webpack v5 #20

Open
blueputty01 opened this issue Feb 25, 2023 · 1 comment
Open

File casing produces error on Webpack v5 #20

blueputty01 opened this issue Feb 25, 2023 · 1 comment

Comments

@blueputty01
Copy link

blueputty01 commented Feb 25, 2023

When building with Webpack v5, the following error is generated (emphasis mine):

✖ 「wdm」: Error: Prevent writing to file that only differs in casing or query string from already written file.
This will lead to a race-condition and corrupted files on case-insensitive file systems.
/home/blueputty01/code/httptoolkit-ui/dist/api/azure.com/azsadmin-quotas.json
/home/blueputty01/code/httptoolkit-ui/dist/api/azure.com/azsadmin-Quotas.json
at checkSimilarFile (/home/blueputty01/code/httptoolkit-ui/node_modules/webpack/lib/Compiler.js:666:11)
at writeOut (/home/blueputty01/code/httptoolkit-ui/node_modules/webpack/lib/Compiler.js:848:11)
at /home/blueputty01/code/httptoolkit-ui/node_modules/webpack/lib/util/fs.js:242:5
at Immediate._onImmediate (/home/blueputty01/code/httptoolkit-ui/node_modules/memory-fs/lib/MemoryFileSystem.js:303:5)
at processImmediate (node:internal/timers:476:21)

When this error is resolved by renaming one of the indicated files eg Quotas to quotas2, subsequent errors for files like sql-databaseSecurityAlertPolicies.json and sql-DatabaseSecurityAlertPolicies.json are generated.

@pimterry
Copy link
Member

Good spot, thanks for reporting this @blueputty01! I think this mainly is an issue for https://github.com/APIs-guru/openapi-directory/, where this data comes from. I've filed an issue upstream to see if we can clean that up and they're looking at that now. We could probably handle this better here too though, I'll look into it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants