Package management about docs HOT 7 CLOSED

Overall, I think I would still vote to use npm. There are some benefits to Yarn 2 for sure, but I think it'll still cause some confusion around versioning, even if corepack is used. I feel like questions like "This project is Yarn 2, but I have Yarn 1. Will it work? What is corepack?" will come up. I could maybe see us relying on it if it were on by default, but it's not quite there yet. npm is a really safe choice and will be fairly familiar for people—I don't think we'd go wrong choosing it.

from docs.

I agree that npm is the safest choice.

WRT Yarn 1 vs 2 I believe how it works is that if they have the latest Yarn 1 it will detect that the project uses a different Yarn (through yarn set version stable a .yarnrc file is generated that latest Yarn Classic will detect and adhere to). So it should "just work", but definitely more fragile than I'd like.

We could keep this issue open and see how yarn/corepack matures and revisit later with some more scientific evaluation of the pros and cons.

from docs.

Is this issue duplicated (more or less) now in Issue #43? @flaki

from docs.

@LauraLangdon yeah the two are closely related. I'll have a look at this again next week and try to come up with a proposal for the weekly meeting.

from docs.

Docusaurus has existing plugin support for displaying npm/yarn commands automatically as tabs.

from docs.

From yesterday's docs meeting notes:

• Laura: The docs should follow the behaviour of respecting the “selected” language, meaning that we should show a “language not available” type of message
• Ramón: Should we show all tabs, even if there’s no content for that language?
• Laura: That makes sense
• Ramón: Why not have a “Contribute this code block” kind of incentive when no code present for that language?
• @flaki Is this possible? Say if the “content” prop is empty, or something?

from docs.

As discussed with @callahad, we'll go with an opinionated ™️ approach and opt for npm:

Those who know yarn will use yarn

from docs.