This repository has been archived by the owner on Mar 18, 2022. It is now read-only.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm slightly confused: The PR description says it's not idiomatic to install nodejs and npm via apt, but that's still what we're doing here, right? Did you mean "install yarn via npm" instead?
Separately, a minor nit: I realize markdown processors will render the text with sequential numbers, but part of the point of Markdown is it should be human-readable even in plain text form. I personally dislike the style of using "1." for every bullet, especially when there are only a few. YMMV.
I'd argue the code fence was preferable, because it was copy-pasteable into the terminal. What do you think about something like:
Having a naked pointer to a long page of mixed-system install instructions seems like a regression to me, and if I read it right you may have to click through to at least one additional page (if your Ubuntu is old enough). Maybe we can just inline the hot path here?