feat: use npm for managing js packages
#571
Draft
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
|
(I've made this a draft for now because I decided I want to migrate a few more apps to ensure everything is smooth before we make it our default out-of-the-box setup) |
G-Rath
force-pushed
the
use-npm
branch
3 times, most recently
from
adce0cd to
c9054fa
Compare
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.
We've decided that we want to use
npmas our package manager for JavaScript dependencies, so this removes our explicit support for the other package managers, though we still remain pretty agnostic due to the use ofPackageJsonwhich I've retained for now given it's lightweight and secretly I'm keen to explorepnpmat some point so this will come in handy if that turns out to be worth switching to 😄I've also retained the "create fake package managers" script + ci step to ensure that we really are only ever using
npm; I plan to explore refactoring that script given we no longer need to support all the package managers as a follow-up since it too is lightweight and perfectly functional as-is.