Repository navigation
Conversation
…cking the yarn launcher yarn and corepack both provide a 'yarn' launcher in the shared global npm prefix. Since devonfw#1545 IDEasy installs global packages with 'npm install -gf', so whichever tool is installed last overwrites the launcher of the other. Instead of relying on the shared PATH launcher, run yarn's own entry point (node <prefix>/node_modules/yarn/bin/yarn.js) via the IDEasy-managed node runtime. Falls back to the previous behavior when the entry point is not available.
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
1 participant
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.
This PR fixes #2627
Implemented changes:
Instead of relying on the shared PATH launcher, run yarn's own entry point (yarn/bin/yarn.js under the npm global prefix) via the IDEasy-managed node runtime. Falls back to the previous behavior when the entry point is not available.
Testing instructions
To confirm the fix, compare the same commands from the issue ticket:
Checklist for this PR
Make sure everything is checked before merging this PR. For further info please also see
our DoD.
mvn clean testlocally all tests pass and build is successful#«issue-id»: «brief summary»(e.g.#921: fixed setup.batand notfeature/921 fixed setup.bat).If no issue ID exists, title only.
In Progressand assigned to you or there is no issue (might happen for very small PRs)with
internalpom.xmlfiles or otherwise if runtime dependencies changed,you have updated our LICENSE.adoc