-
-
Notifications
You must be signed in to change notification settings - Fork 561
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
[Bug]: cacheGroups
filename params with maxSize
doesn't take effect
#6440
Comments
Actually, no part of the name configuration takes effect EX:
Produces
|
maxSize
doesn't take effectcacheGroups
filename params with maxSize
doesn't take effect
I could not reproduce this issue. Please provide a minimal reproduction repository. @abettadapur |
Thanks for looking @SyMind . |
@SyMind I'm having trouble creating a repro, but I can still reproduce the issue in my codebase For more context, I think the issue only occurs in development mode, where RSPack seems to try to use the loader name as part of the chunk name. For this particular cacheGroup, I am using a custom loader in my configuration, which is producing the above issue, even on v0.7.5 However, even in my repro repository, RSPack seems to use |
My attempt at a repro here: https://github.com/abettadapur/rspack-chunk-repro |
@SyMind could you point me to where these cache group names are generated? I can try to debug on my end |
@abettadapur I will work on this issue this week. |
I ran both |
This issue has been automatically marked as stale because it has not had recent activity. If this issue is still affecting you, please leave any comment (for example, "bump"). We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment! |
System Info
System: All
Version: RSPack 0.6.3
Details
I have the following
cacheGroups
configurationWith webpack, I get the following files
With RSPack, I get the following files
I would expect
[contentHash]
to take effect hereReproduce link
No response
Reproduce Steps
Add a
cacheGroups
entry, and set max size so multiple chunks are producedSee that
[contentHash]
is not respectedThe text was updated successfully, but these errors were encountered: