Switch to NPM by default and away from a Yarn dependency #869
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.
As previously announced, Bridgetown 2.0 is switching to NPM by default (included with Node of course) and away from an additional dependency on Yarn--though support for Yarn as well as pnpm are still provided for projects which use them.
This PR also tries to abstract out any automations (for bundled configurations, adding packages to match gems for plugins, etc.) so they work for NPM, Yarn, pnpm, and any other potential choices down the road. And we're now standardizing on Node v20 minimum.
For further context read: https://www.bridgetownrb.com/future/road-to-bridgetown-2.0-new-baselines/
We may also want to expose a customization option for new projects, see #609