[Fix] Switch from yarn to npm #767
Merged
Conversation
This file contains 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
Riippi
force-pushed
the
fix/yarn-to-npm
branch
from
1211f61 to
f9346a2
Compare
Riippi
force-pushed
the
fix/yarn-to-npm
branch
from
f9346a2 to
b19fd67
Compare
LJKaski
approved these changes
Sep 15, 2023
Merged
Merged
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.
Description
Remove yarn from scripts and documentation. Start using npm instead.
Related Issue
Closes # https://jira.dvv.fi/browse/SFIDS-861
Motivation and Context
Currently yarn doesn't offer any significant benefits compared to npm.
Instead yarn has some issues with updating the dependency tree in this project that npm doesn't.
How Has This Been Tested?
Running package.json commands with npm. CircleCI.
Vercaccio + own project
Release notes