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
chunkFileNames
needs to be case sensitive
#3139
Comments
Not sure I understand you correctly. At the moment the names ARE case sensitive in that |
No, I meant that for example Date.js and date.js gets combined to date.js for some reason, so currently, it is insensitive. We need it to make it sensitive for all cases. I'm not exactly sure what causes this case-insensitivity, but when I remove the option |
As you are on a Mac, I would assume you are on a case-insensitive file system as this is the default. That means that when there is a file on the disk named date.js and you store a file named Date.js, then that will replace the existing file. My guess is that it is not Rollup that is replacing the file but your operating system. The reason is that Rollup is, as far as I know, case-sensitive, which means that it thinks date.js and Date.js are different file names and there is no reason to change one of the names before writing to disk (you could check by inspecting the bundle passed to the generateBundle hook if it has separate entries for the two files). The only people for whom this would be the correct choice, though, would be Linux users and some Mac users that specifically chose a case-sensitive file system, so case-insensitive deduplication by default would definitely be the prudent choice. |
@lukastaegert Consider we have two virtual modules named I'm trying to fix this issue #3317, but don't know why CI are failed, could you have a look. |
How Do We Reproduce?
config
chunkFileNames: '[name].js',
Expected Behavior
It is expected to generate name which is case sensitive.
Actual Behavior
It is generating
Date.js
anddate.js
the same asdate.js
and it confuses the bundle.The text was updated successfully, but these errors were encountered: