make docs more generic to package managers #4310
Conversation
for a long time NPM has basically been the de facto front end package manager. however, BunJS is making a strong push, and a good case for itself, so I think it'd be good for us to include it where appropriate. we all know specific tooling comes and goes, so I've made the language *more generic* where appropriate, and refer to "a package manager" instead of specifically "NPM". I've also then included the analogous `bun` command next to `npm` commands.
|
|
|
I'm definitely okay with adding others, if you want to do a separate PR after/if this one gets merged. I still think it's important to make the appropriate parts of the documentation language "tool agnostic". What do you mean by "bun is not supported many places"? It's a binary that can be installed with a simple bash script. |
I mean naturally. Like auto-detected, preinstalled.
Probably better just to do it all in one, tbh. |
for a long time NPM has basically been the de facto front end package manager. however, BunJS is making a strong push, and a good case for itself, so I think it'd be good for us to include it where appropriate.
we all know specific tooling comes and goes, so I've made the language more generic where appropriate, and refer to "a package manager" instead of specifically "NPM".
I've also then included the analogous
buncommand next tonpmcommands.