Repository navigation
fix: rename duplicate hasForce declaration blocking all releases - #1028
Merged
Merged
Conversation
The esbuild bundler flattened two separate function scopes into one, creating two 'const hasForce' declarations (lines 1130 and 1192). This causes a SyntaxError on load, failing 90/130 tests and blocking every release run on main. Renamed the second declaration to 'shouldForce' to resolve the conflict. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
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.
Problem
Every release run on main fails with a SyntaxError: duplicate const hasForce declaration in index.cjs (lines 1130 and 1192). The esbuild bundler flattened two separate function scopes into one, creating the conflict. 90/130 tests fail because index.cjs can't load at all.
This has been blocking every single release - v0.9.4 hasn't made it to npm latest.
Fix
Renamed the second hasForce (line 1192) to shouldForce. They serve different purposes:
Impact
Once merged, the release pipeline should pass and publish v0.9.4 to npm.