diff --git a/BUILDING.md b/BUILDING.md index a4a00a9f1ffe49..a7dc040f5f385e 100644 --- a/BUILDING.md +++ b/BUILDING.md @@ -204,7 +204,7 @@ For use of AVX2, * nasm version 2.10 or higher in Windows Please refer to - https://www.openssl.org/docs/man1.1.1/man3/OPENSSL_ia32cap.html for details. + for details. If compiling without one of the above, use `configure` with the `--openssl-no-asm` flag. Otherwise, `configure` will fail. @@ -277,7 +277,7 @@ $ make -j4 If you run into a `No module named 'distutils.spawn'` error when executing `./configure`, please try `python3 -m pip install --upgrade setuptools` or `sudo apt install python3-distutils -y`. -For more information, see https://github.com/nodejs/node/issues/30189. +For more information, see . The `-j4` option will cause `make` to run 4 simultaneous compilation jobs which may reduce build time. For more information, see the diff --git a/README.md b/README.md index 0048be118c988c..0542c5c7b26a11 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,4 @@ +

### DEP0122: `tls` `Server.prototype.setOptions()` diff --git a/doc/api/errors.md b/doc/api/errors.md index 5308490b88fe8c..480bbdfbd23e42 100644 --- a/doc/api/errors.md +++ b/doc/api/errors.md @@ -1194,7 +1194,7 @@ is set for the `Http2Stream`. ### `ERR_INTERNAL_ASSERTION` There was a bug in Node.js or incorrect usage of Node.js internals. -To fix the error, open an issue at https://github.com/nodejs/node/issues. +To fix the error, open an issue at . ### `ERR_INCOMPATIBLE_OPTION_PAIR` diff --git a/doc/api/os.md b/doc/api/os.md index 27a7c3d549f78b..e2cce1f8a5580f 100644 --- a/doc/api/os.md +++ b/doc/api/os.md @@ -290,7 +290,7 @@ Returns the operating system as a string. On POSIX systems, the operating system release is determined by calling [uname(3)][]. On Windows, `GetVersionExW()` is used. See -https://en.wikipedia.org/wiki/Uname#Examples for more information. + for more information. ## `os.setPriority([pid, ]priority)` + diff --git a/doc/changelogs/CHANGELOG_IOJS.md b/doc/changelogs/CHANGELOG_IOJS.md index e736a70dedfef2..0a650253182b6d 100644 --- a/doc/changelogs/CHANGELOG_IOJS.md +++ b/doc/changelogs/CHANGELOG_IOJS.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V010.md b/doc/changelogs/CHANGELOG_V010.md index 65b6bef55bbd20..d4b579e6b5b88b 100644 --- a/doc/changelogs/CHANGELOG_V010.md +++ b/doc/changelogs/CHANGELOG_V010.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V012.md b/doc/changelogs/CHANGELOG_V012.md index 8a5ebf3e429fa6..d0485ffc58f652 100644 --- a/doc/changelogs/CHANGELOG_V012.md +++ b/doc/changelogs/CHANGELOG_V012.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V10.md b/doc/changelogs/CHANGELOG_V10.md index e347b51619e6d8..8a3baae0a53c57 100644 --- a/doc/changelogs/CHANGELOG_V10.md +++ b/doc/changelogs/CHANGELOG_V10.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V11.md b/doc/changelogs/CHANGELOG_V11.md index 960276df5e0293..be1cd8102e74a5 100644 --- a/doc/changelogs/CHANGELOG_V11.md +++ b/doc/changelogs/CHANGELOG_V11.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V12.md b/doc/changelogs/CHANGELOG_V12.md index 28e0c6ec306316..e3a457c39f18c6 100644 --- a/doc/changelogs/CHANGELOG_V12.md +++ b/doc/changelogs/CHANGELOG_V12.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V13.md b/doc/changelogs/CHANGELOG_V13.md index 3c2d64e2d960ee..285120dcae8ebf 100644 --- a/doc/changelogs/CHANGELOG_V13.md +++ b/doc/changelogs/CHANGELOG_V13.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V4.md b/doc/changelogs/CHANGELOG_V4.md index 2f5c81319025c7..69f36cf2cea9d9 100644 --- a/doc/changelogs/CHANGELOG_V4.md +++ b/doc/changelogs/CHANGELOG_V4.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V5.md b/doc/changelogs/CHANGELOG_V5.md index ac338886c858c6..c9cd28d692bfaf 100644 --- a/doc/changelogs/CHANGELOG_V5.md +++ b/doc/changelogs/CHANGELOG_V5.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V6.md b/doc/changelogs/CHANGELOG_V6.md index 763ff802884781..20c9370ff0d5ab 100644 --- a/doc/changelogs/CHANGELOG_V6.md +++ b/doc/changelogs/CHANGELOG_V6.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V7.md b/doc/changelogs/CHANGELOG_V7.md index 5a06890f58685b..a64b973c8c2192 100644 --- a/doc/changelogs/CHANGELOG_V7.md +++ b/doc/changelogs/CHANGELOG_V7.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V8.md b/doc/changelogs/CHANGELOG_V8.md index 33fa32948389b6..41e38efcf57206 100644 --- a/doc/changelogs/CHANGELOG_V8.md +++ b/doc/changelogs/CHANGELOG_V8.md @@ -2,6 +2,7 @@ +
diff --git a/doc/changelogs/CHANGELOG_V9.md b/doc/changelogs/CHANGELOG_V9.md index f58341bb34b52d..e4cdf50a9381b6 100644 --- a/doc/changelogs/CHANGELOG_V9.md +++ b/doc/changelogs/CHANGELOG_V9.md @@ -2,6 +2,7 @@ +
diff --git a/doc/guides/cve-management-process.md b/doc/guides/cve-management-process.md index 1b87215ac722f2..eba94484b53877 100644 --- a/doc/guides/cve-management-process.md +++ b/doc/guides/cve-management-process.md @@ -3,7 +3,7 @@ The Node.js project acts as a [Common Vulnerabilities and Exposures (CVE) Numbering Authority (CNA)](https://cve.mitre.org/cve/cna.html). The current scope is for all actively developed versions of software -developed under the Node.js project (ie. https://github.com/nodejs). +developed under the Node.js project (ie. ). This means that the Node.js team reviews CVE requests and if appropriate assigns CVE numbers to vulnerabilities. The scope currently **does not** include third party modules. @@ -18,17 +18,17 @@ of contact points. Email aliases have been setup for these as follows: * **Public contact points**. Email address to which people will be directed by Mitre when they are asked for a way to contact the Node.js team about - CVE-related issues. **cve-request@iojs.org** + CVE-related issues. **[cve-request@iojs.org][]** * **Private contact points**. Administrative contacts that Mitre can reach out to directly in case there are issues that require immediate attention. - **cve-mitre-contact@iojs.org** + **[cve-mitre-contact@iojs.org][]** * **Email addresses to add to the CNA email discussion list**. This address has been added to a closed mailing list that is used for announcements, sharing documents, or discussion relevant to the CNA community. The list rarely has more than ten messages a week. - **cna-discussion-list@iojs.org** + **[cna-discussion-list@iojs.org][]** ## CNA management processes @@ -56,7 +56,7 @@ as outlined in the section titled `CVE Management process`. In addition, when moving a CVE from Available such that there are less than two remaining CVEs a new block must be requested as follows: -* Use the Mitre request form https://cveform.mitre.org/ with the +* Use the Mitre request form with the option `Request a Block of IDs` to request a new block. * The new block will be sent to the requester through email. * Once the new block has been received, the requester will add them @@ -72,7 +72,7 @@ of CVEs should then be requested using the steps listed above. ### External CVE request process -When a request for a CVE is received via the cve-request@iojs.org +When a request for a CVE is received via the [cve-request@iojs.org][] email alias the following process will be followed (likely updated after we get HackerOne up and running). @@ -135,3 +135,7 @@ following steps are used to assign, announce and report a CVE. * Move the CVE from the Pending section to the Announced section along with a link to the Node.js blog post announcing that releases are available. + +[cve-request@iojs.org]: mailto:cve-request@iojs.org +[cve-mitre-contact@iojs.org]: mailto:cve-mitre-contact@iojs.org +[cna-discussion-list@iojs.org]: mailto:cna-discussion-list@iojs.org diff --git a/doc/guides/maintaining-openssl.md b/doc/guides/maintaining-openssl.md index 5be6a5f5e2cd10..5bfe01e0f61b56 100644 --- a/doc/guides/maintaining-openssl.md +++ b/doc/guides/maintaining-openssl.md @@ -5,7 +5,7 @@ This document describes how to update `deps/openssl/`. ## Requirements * Linux environment * `perl` Only Perl version 5 is tested. -* `nasm` (http://www.nasm.us/) The version of 2.11 or higher is needed. +* `nasm` () The version of 2.11 or higher is needed. * GNU `as` in binutils. The version of 2.26 or higher is needed. ## 0. Check Requirements @@ -27,7 +27,7 @@ NASM version 2.11.08 ## 1. Obtain and extract new OpenSSL sources -Get a new source from https://www.openssl.org/source/ and extract +Get a new source from and extract all files into `deps/openssl/openssl`. Then add all files and commit them. ```sh diff --git a/doc/guides/offboarding.md b/doc/guides/offboarding.md index 3db892b0f3de3d..13f602bb0f8286 100644 --- a/doc/guides/offboarding.md +++ b/doc/guides/offboarding.md @@ -13,4 +13,4 @@ Emeritus or leaves the project. * Some teams may also require a pull request to remove the Collaborator from a team listing. For example, if someone is removed from @nodejs/build, they should also be removed from the Build WG README.md file in the - https://github.com/nodejs/build repository. + repository. diff --git a/doc/guides/releases.md b/doc/guides/releases.md index 2068a46dc111e4..141a264d5123ab 100644 --- a/doc/guides/releases.md +++ b/doc/guides/releases.md @@ -682,7 +682,7 @@ The nodejs.org website will automatically rebuild and include the new version. To announce the build on Twitter through the official @nodejs account, email [pr@nodejs.org](mailto:pr@nodejs.org) with a message such as: -> v5.8.0 of @nodejs is out: https://nodejs.org/en/blog/release/v5.8.0/ +> v5.8.0 of @nodejs is out: > … > something here about notable changes diff --git a/doc/guides/security-release-process.md b/doc/guides/security-release-process.md index 73d27ae7c60d8c..acf6b56558e3ae 100644 --- a/doc/guides/security-release-process.md +++ b/doc/guides/security-release-process.md @@ -88,6 +88,6 @@ information described. * [ ] Make sure the PRs for the vulnerabilities are closed. [H1 CVE requests]: https://hackerone.com/nodejs/cve_requests -[docker-node]: https://github.com/nodejs/docker-node/issues) -[nodejs/build]: https://github.com/nodejs/build/issues) +[docker-node]: https://github.com/nodejs/docker-node/issues +[nodejs/build]: https://github.com/nodejs/build/issues [email]: https://groups.google.com/forum/#!forum/nodejs-sec diff --git a/doc/guides/using-symbols.md b/doc/guides/using-symbols.md index b4bf9cd67f4081..2bc32862b7169e 100644 --- a/doc/guides/using-symbols.md +++ b/doc/guides/using-symbols.md @@ -9,7 +9,7 @@ Symbol-keyed properties of an object are not included in the output of default. Learn more about symbols at -https://developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Symbol. +. ## `Symbol(string)` diff --git a/doc/guides/writing-and-running-benchmarks.md b/doc/guides/writing-and-running-benchmarks.md index 0075023ce80fa8..eca55bf4edf2ea 100644 --- a/doc/guides/writing-and-running-benchmarks.md +++ b/doc/guides/writing-and-running-benchmarks.md @@ -54,7 +54,7 @@ from [nghttp2.org][] or built from source. ### Benchmark Analysis Requirements To analyze the results, `R` should be installed. Use one of the available -package managers or download it from https://www.r-project.org/. +package managers or download it from . The R packages `ggplot2` and `plyr` are also used and can be installed using the R REPL. @@ -68,7 +68,7 @@ install.packages("plyr") In the event that a message is reported stating that a CRAN mirror must be selected first, specify a mirror by adding in the repo parameter. -If we used the "http://cran.us.r-project.org" mirror, it could look something +If we used the "" mirror, it could look something like this: ```R diff --git a/doc/guides/writing-tests.md b/doc/guides/writing-tests.md index 7022bf8f938f78..385e3813fdbd69 100644 --- a/doc/guides/writing-tests.md +++ b/doc/guides/writing-tests.md @@ -430,7 +430,7 @@ To generate a test coverage report, see the [Test Coverage section of the Building guide][]. Nightly coverage reports for the Node.js master branch are available at -https://coverage.nodejs.org/. +. [ASCII]: http://man7.org/linux/man-pages/man7/ascii.7.html [Google Test]: https://github.com/google/googletest diff --git a/glossary.md b/glossary.md index a48fd6083b407f..a2954635a5ce93 100644 --- a/glossary.md +++ b/glossary.md @@ -1,4 +1,4 @@ -You may also need to check https://chromium.googlesource.com/chromiumos/docs/+/master/glossary.md. +You may also need to check . * LGTM: "Looks good to me", commonly used to approve a code review. * PTAL: Please take a look. diff --git a/onboarding.md b/onboarding.md index 4f1346f2d06600..31b8353ef41ec5 100644 --- a/onboarding.md +++ b/onboarding.md @@ -165,7 +165,7 @@ onboarding session. * It is not automatically run. You need to start it manually. * Log in on CI is integrated with GitHub. Try to log in now! * You will be using `node-test-pull-request` most of the time. Go there now! - * Consider bookmarking it: https://ci.nodejs.org/job/node-test-pull-request/ + * Consider bookmarking it: * To get to the form to start a job, click on `Build with Parameters`. (If you don't see it, that probably means you are not logged in!) Click it now! * To start CI testing from this screen, you need to fill in two elements on @@ -200,7 +200,7 @@ needs to be pointed out separately during the onboarding. ## Exercise: Make a PR adding yourself to the README * Example: - https://github.com/nodejs/node/commit/ce986de829457c39257cd205067602e765768fb0 + * For raw commit message: `git log ce986de829457c39257cd205067602e765768fb0 -1` * Collaborators are in alphabetical order by GitHub username. diff --git a/tools/icu/README.md b/tools/icu/README.md index 01b0178c454a8b..e59f28b71801b7 100644 --- a/tools/icu/README.md +++ b/tools/icu/README.md @@ -21,7 +21,7 @@ Note: > The files in this directory were written for the Node.js v0.12 effort. > The original intent was to merge the tools such as `icutrim.py` and `iculslocs.cc` > back into ICU. ICU has gained its own “data slicer” tool. -> There is an issue open, https://github.com/nodejs/node/issues/25136 +> There is an issue open, > for replacing `icutrim.py` with the [ICU data slicer][]. ## See Also