From npm to Yarn and back again #73
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
Some years ago I switched from npm [1] (`v4`) to Yarn [2] (`v1`) mainly because of the fantastic workspace feature [3] for monorepos [4] as well as the great performance and UX improvements. This was a good decision and almost every popular and well-known project used to do the same, but with the announcement of Yarn v2 [5] (named "berry" [6]) the community got upset about the path the project has taken. Next to this, npm joined GitHub [7] back in March 2020 which meant that the development continues in a good direction and is baked by the open source platform itself. These events, the overall fantastic new npm release version `v7`, including the introduction of workspaces [8], and the fact that I never liked the disadvantage of requiring to use an "external" package manager instead of the one that is bundled with Node, lead to the decision to finally switch back to npm again. The only drawback is the constraint that the minimum npm version must be `v7.7.0` [9] because this is the first version that comes with workspace support for the `run-script` and `exec` commands through the `--workspace`/`-w` and `--workspaces`/`-ws` CLI flags, e.g. `npm run -w PACKAGE run lint`. The first Node version that ships with npm `v7.7.x` is `v15.13.0` [10] which is globally available as of April 1, 2021 (no, it's not an april fool). To ensure that these constraints are met, without only relying on users to read the documentation, both `npm` and `node` will be added to the `engines` field [11] of the `package.json` file. This change also requires updates to all documentations, including the addition of the version constraints, as well as updates to repository template features like the GitHub Action workflows. The `.yarnrc` file will be replaced by `.npmrc` that includes the `package-lock=false` and `save-exact=false` configurations. [1]: https://www.npmjs.com [2]: https://classic.yarnpkg.com [4]: https://en.wikipedia.org/wiki/Monorepo [5]: https://yarnpkg.com [6]: https://github.com/yarnpkg/berry [7]: https://github.blog/2020-03-16-npm-is-joining-github [8]: https://docs.npmjs.com/cli/v7/using-npm/workspaces [9]: https://github.com/npm/cli/releases/tag/v7.7.0 [10]: https://nodejs.org/dist/v15.13.0 [11]: https://docs.npmjs.com/cli/v7/configuring-npm/package-json#engines GH-72
arcticicestudio
approved these changes
Apr 1, 2021
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.
Resolves #72