feat(TU-33149): Remove pinned yarn 1.18.0 #720
Merged
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
releaseworkflow failing with npm error LRU is not a constructor.Investigation
yarn 1.18.0'shoisting causedsemver@7.5.2to resolvelru-cache@11.xinstead of^6.0.0. The API changed between versions (new LRU() → new LRUCache()), causing the crash (couldn't find its ownlru-cache@6in its nestednode_modules, so Node's resolution walked up and found the rootlru-cache@11instead).js-api-clientworks because it uses system yarn1.22.xwith correct hoisting.Fix
1.18.0 (.yarnrc, .yarn/releases/)yarn.lock@typeform/eslint-config@6.0.3and@visual-regression-tracker/agent-cypress@5.6.0to prevent breaking upgrades@types/minimatch@5.1.2packages/demo-nextjs/yarn.lock