doc: final round of markdown format changes · nodejs/node@82facfb · GitHub
Skip to content

Commit 82facfb

Browse files
Trottdanielleadams
Trott
authored and
danielleadams
committed
doc: final round of markdown format changes
Once the README and find-inactive-collaborators.mjs changes land here, we can introduce markdown formatting as a step in the toolchain somewhere. Before this lands, nodejs/node-core-utils#578 will need to land and be included in a node-core-utils release. PR-URL: #40645 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Michaël Zasso <targos@protonmail.com>
1 parent fe1b6fb commit 82facfb

10 files changed

Lines changed: 2444 additions & 272 deletions

File tree

‎README.md‎

Lines changed: 245 additions & 245 deletions
Large diffs are not rendered by default.

‎doc/api/esm.md‎

Lines changed: 16 additions & 16 deletions

‎doc/api/n-api.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1009,8 +1009,8 @@ The content of the `napi_extended_error_info` returned is only valid up until
10091009
a Node-API function is called on the same `env`. This includes a call to
10101010
`napi_is_exception_pending` so it may often be necessary to make a copy
10111011
of the information so that it can be used later. The pointer returned
1012-
in error_message points to a statically defined string so it is safe to use
1013-
that pointer if you have copied it out of the error_message field (which will
1012+
in `error_message` points to a statically-defined string so it is safe to use
1013+
that pointer if you have copied it out of the `error_message` field (which will
10141014
be overwritten) before another Node-API function was called.
10151015

10161016
Do not rely on the content or format of any of the extended information as it

‎doc/changelogs/CHANGELOG_V12.md‎

Lines changed: 149 additions & 0 deletions

0 commit comments

Comments
 (0)