Stop emitting pathinfo in production to limit heap size - #6077
Merged
Conversation
DXCanas
approved these changes
Aug 3, 2026
DXCanas
left a comment
DXCanas
left a comment
Member
There was a problem hiding this comment.
No idea
but I like that it's a single-character change, and the promised impact of that change
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Reviewer guidance
Confirm the build passes on CI.
See here: https://webpack.js.org/configuration/output/#outputpathinfo
AI usage
Used Claude to experiment with a few different possibilities, removing pathinfo from prod, using parallel webpack configurations, and increasing the max heap size for NodeJS. Ended up using pathinfo because it worked and was least intrusive, and seemed to just be an error from previous tweaks.