Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

correct the version of node required #215

Merged
merged 5 commits into from
Oct 8, 2020
Merged

correct the version of node required #215

merged 5 commits into from
Oct 8, 2020

Conversation

jeffmcaffer
Copy link
Contributor

Why:

stated version of node was 14 when it's actually 12

What's being changed:

fix the doc

Check off the following:

Copy link
Contributor

@zeke zeke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. 👍🏼

I made some additional changes to clarify exactly which Node.js versions are required or used in each environment.

The site currently runs on Node.js v14, the [Active LTS version](https://nodejs.org/en/about/releases/) from 2020-10-27 to 2021-10-26.
In [development](contributing/development.md) enviroments this site will run on Node.js versions `12 - 14`.

In [staging and production](contributing/deployments.md) environments this site runs on Node.js 14, the [Active LTS version](https://nodejs.org/en/about/releases/) from 2020-10-27 to 2021-10-26).
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it's a bit odd to say that Node 14 is the Active LTS when it's not. Perhaps just remove the qualification and say "this site runs on the latest in the Node.js 14 family" (or Node.js 14.* as undoubtedly there will be a gap between a new 14.* coming out and us deploying).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's not the Active LTS now, but it will be in 3 weeks. Hence the from 2020-10-27 to 2021-10-26.

@@ -8,7 +8,7 @@ This site is powered by Node.js! :sparkles: :turtle: :rocket: :sparkles:

It runs on macOS, Windows, and Linux environments.

You'll need **Node.js v14** to run the site. If you're using [`nodenv`](https://github.com/nodenv/nodenv), read the [`nodenv` docs](#nodenv) for instructions on switching Node.js versions. If you're not using `nodenv`, the best way to install Node.js is to [download the LTS installer from nodejs.org](https://nodejs.org).
You'll need Node.js version `12 - 14` to run the site. To install Node.js, [download the "LTS" installer from nodejs.org](https://nodejs.org). If you're using [`nodenv`](https://github.com/nodenv/nodenv), read the [`nodenv` docs](#nodenv) for instructions on switching Node.js versions.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

consider using non-technical terms to talk about the versions. For example, for people not familiar with the Node versioning scheme, 12 - 14 could look like an actual version number. Whereas what I think you mean is "any stable version from 12 on".

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I chose the literal 12 - 14 string because it's explicit. I can change that to "Node.js versions 12 to 14`

We don't actually mean "any stable version from 12 on". If anyone tries to run the site on something greater than Node 14, it won't run.

@janiceilene janiceilene added the engineering Will involve Docs Engineering label Oct 8, 2020
@zeke
Copy link
Contributor

zeke commented Oct 8, 2020

@jeffmcaffer I tweaked the wording based on your suggestions. Gonna ship this when it turns green.

@zeke zeke merged commit e666d05 into main Oct 8, 2020
@zeke zeke deleted the jeffmcaffer-patch-1 branch October 8, 2020 19:28
@github-actions
Copy link
Contributor

github-actions bot commented Oct 8, 2020

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours.

If you haven't already, you can add yourself to the list of contributors by creating a new comment in this PR using these instructions. Thanks again! ✨

Copy link

@Abhishek577270 Abhishek577270 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

218<

jnidzwetzki pushed a commit to jnidzwetzki/docs that referenced this pull request Oct 6, 2022
* New issues from Moz, plus some general tidy-up

* Issue github#222

* Issue github#215 & remove unused links

* Others from Moz

* Moar 404s, syntax, etc.

* make fixing changes to links

Co-authored-by: Miranda Auhl <miranda@timescale.com>
Co-authored-by: Ryan Booz <ryan@timescale.com>
@Link- Link- mentioned this pull request Mar 29, 2023
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Will involve Docs Engineering
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants