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.

Sign up for GitHub

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

Jump to bottom

doc: fix nits in blog/release/v8.0.0.md #1244

Merged
merged 1 commit into from
May 31, 2017
Merged

doc: fix nits in blog/release/v8.0.0.md #1244

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 6 additions & 6 deletions locale/en/blog/release/v8.0.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -200,12 +200,12 @@ AssertionError [ERR_ASSERTION]: false == true

Information for static error codes can be queried quickly by referencing the
Node.js documentation. For instance, the URL to lookup information about the
`ERR_ASSERTION` error code is
https://nodejs.org/dist/latest-v7.x/docs/api/errors.html#ERR_ASSERTION.
`ERR_ARG_NOT_ITERABLE` error code is
Copy link
Member

@jasnell jasnell May 30, 2017 •
edited
Loading

Choose a reason for hiding this comment

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

I could have sworn that ERR_ASSERTION had been added... will have to make sure it is.

The link format does work tho... try

https://nodejs.org/dist/latest-v8.x/docs/api/errors.html#ERR_ARG_NOT_ITERABLE

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done)

https://nodejs.org/dist/latest-v8.x/docs/api/errors.html#ERR_ARG_NOT_ITERABLE.

### Redirecting Process Warnings

Processing warnings such as deprecations may now to redirected to a file by
Processing warnings such as deprecations may now be redirected to a file by
using either the `--redirect-warnings={file}` command line argument or matching
`NODE_REDIRECT_WARNINGS={file}` environment variable. Rather than printing
warnings out to `stderr` by default, warnings will be written out to the
Expand Down Expand Up @@ -299,8 +299,8 @@ we've dropped the "v" and call it Node.js 8.

* **Dependencies**
* The npm client has been updated to 5.0.0
[[`3c3b36af0f`](https://github.com/nodejs/node/commit/3c3b36af0f)]
[#12936](https://github.com/nodejs/node/pull/12936).
[[`c58cea5`](https://github.com/nodejs/node/commit/c58cea5)]
[#13276](https://github.com/nodejs/node/pull/13276).
* V8 has been updated to 5.8 with forward ABI stability to 6.0
[[`60d1aac8d2`](https://github.com/nodejs/node/commit/60d1aac8d2)]
[#12784](https://github.com/nodejs/node/pull/12784).
Expand Down Expand Up @@ -366,7 +366,7 @@ we've dropped the "v" and call it Node.js 8.

* **Src**
* `NODE_MODULE_VERSION` has been updated to 57
(https://github.com/nodejs/node/commit/ec7cbaf266)]
[[`ec7cbaf266`](https://github.com/nodejs/node/commit/ec7cbaf266)]
[#12995](https://github.com/nodejs/node/pull/12995).
* Add `--pending-deprecation` command-line argument and
`NODE_PENDING_DEPRECATION` environment variable
Expand Down