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.
Proposed Change
Switch from yarn classic to npm.
Reasons
tiny-invariant
with the goal to verify that the library can be consumed in different JS/TS projects. This will involve publishing the package to Verdaccio, and just using npm makes this stuff a little bit easier :)Risks
IMHO none.
npm
re-uses the information fromyarn.lock
when buildingpackage-lock.json
, so when working as a maintainer ontiny-invariant
, dependencies should still be exactly the same as before. I looked into a couple of dependencies to verify that.And for package consumers the lock files don't play any role anyways.
Oh, and one more thing
I removed the
build:flow
script because that was broken anyways. It tried to copy a filesrc/tiny-invariant.js.flow
to thedist
folder, but the name of the flow file issrc/tiny-invariant.flow.js
(the .flow and .js suffix are switched).