meta: use absolute urls for external links

pages/en/blog/announcements/foundation-v4-announce.md

@@ -12,7 +12,7 @@ SAN FRANCISCO, Sept. 14, 2015 – The [Node.js Foundation](https://foundation.no
 
 Currently, Node.js is used by tens of thousands of organizations in more than 200 countries and amasses more than 2 million downloads per month. With major stability and security updates, a new test cluster, support for ARM processors and long-term support, Node.js v4 represents the latest framework innovation for enterprise users leveraging it to run JavaScript programs.
 
-Named version 4.0.0 because it includes major updates from io.js version 3.0.0, the new release also contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays (Node's Buffer is now backed by Uint8Array), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and new to V8 v4.5, arrow functions.
+Named version 4.0.0 because it includes major updates from io.js version 3.0.0, the new release also contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](https://nodejs.org/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays (Node's Buffer is now backed by Uint8Array), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and new to V8 v4.5, arrow functions.
 
 Node.js v4 also brings a plan for [long-term support (LTS)](https://github.com/nodejs/LTS/) and a regular release cycle. Release versioning now follows the Semantic Versioning Specification, a specification for version numbers of software libraries and similar dependencies, so expect increments of both minor and patch version over the coming weeks as bugs are fixed and features are added. The LTS will support enterprise users that need more long-term requirements and continue the innovation and work with the V8 team to ensure that Node.js continues to evolve.
 

pages/en/blog/release/v20.6.0.md

@@ -53,7 +53,7 @@ This feature was contributed by Antoine du Hamel in <https://github.com/nodejs/n
 
 #### Node.js C++ addons now have experimental support for cppgc (Oilpan), a C++ garbage collection library in V8.
 
-Now when Node.js starts up, it makes sure that there is a `v8::CppHeap` attached to the V8 isolate. This enables users to allocate in the `v8::CppHeap` using `<cppgc/*>` headers from V8, which are now also included into the Node.js headers available to addons. Note that since Node.js only bundles the cppgc library coming from V8, [the ABI stability](/docs/guides/abi-stability#abi-stability-in-nodejs) of cppgc is currently not guaranteed in semver-minor and -patch updates, but we do not expect the ABI to break often, as it has been stable and battle-tested in Chromium for years. We may consider including cppgc into the ABI stability guarantees when it gets enough adoption internally and externally.
+Now when Node.js starts up, it makes sure that there is a `v8::CppHeap` attached to the V8 isolate. This enables users to allocate in the `v8::CppHeap` using `<cppgc/*>` headers from V8, which are now also included into the Node.js headers available to addons. Note that since Node.js only bundles the cppgc library coming from V8, [the ABI stability](https://nodejs.org/docs/guides/abi-stability#abi-stability-in-nodejs) of cppgc is currently not guaranteed in semver-minor and -patch updates, but we do not expect the ABI to break often, as it has been stable and battle-tested in Chromium for years. We may consider including cppgc into the ABI stability guarantees when it gets enough adoption internally and externally.
 
 To help addon authors create JavaScript-to-C++ references of which V8's garbage collector can be aware, a helper function [`node::SetCppgcReference(isolate, js_object, cppgc_object)`](https://github.com/nodejs/node/blob/v20.6.0/test/addons/cppgc-object/binding.cc) has been added to `node.h`. V8 may provide a native alternative in the future, which could then replace this Node.js-specific helper. In the mean time, users can use this API to avoid having to hard-code the layout of JavaScript wrapper objects. An example of how to create garbage-collected C++ objects in the unified heap and wrap it in a JavaScript object can be found in the [Node.js addon tests](https://github.com/nodejs/node/blob/v20.6.0/test/addons/cppgc-object/binding.cc).
 

pages/en/blog/release/v4.0.0.md

@@ -8,7 +8,7 @@ author: The Node.js Project
 
 The collaborators of the Node.js project and the members of the Node.js Foundation are proud to offer v4.0.0 for general release. This release represents countless hours of hard work encapsulated in both the Node.js project and the io.js project that are now combined in a single codebase. The Node.js project is now operated by a team of 44 collaborators, 15 of which form its Technical Steering Committee (TSC). Further, over 100 new individuals have been added to the list of people contributing code to core since v0.12.7.
 
-Node.js v4.0.0 contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays (Node's `Buffer` is now backed by `Uint8Array`), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and, new to V8 v4.5, arrow functions.
+Node.js v4.0.0 contains V8 v4.5, the same version of V8 shipping with the Chrome web browser today. This brings with it many bonuses for Node.js users, most notably a raft of new [ES6](https://nodejs.org/docs/es6/) features that are enabled by default including block scoping, classes, typed arrays (Node's `Buffer` is now backed by `Uint8Array`), generators, Promises, Symbols, template strings, collections (Map, Set, etc.) and, new to V8 v4.5, arrow functions.
 
 Over the past year thanks to donations from companies such as Rackspace, DigitalOcean, Scaleway, miniNodes, Voxer, Joyent, CloudFlare, ARM Holdings, and individuals from the community, we've built an amazing test cluster that includes an impressive line-up of Linux variants, OS X, Windows, FreeBSD and SmartOS. New to Node.js, we also have first-class support for ARM processors. Our test suite must be continually passing on ARMv6, ARMv7 and the new 64-bit ARMv8 processors. So Node.js is officially ready for use by hobbyists and ARM server users alike.
 

pages/en/blog/release/v8.0.0.md

@@ -52,7 +52,7 @@ as well.
 The [N-API](https://nodejs.org/api/n-api.html) is experimental in Node.js 8.0.0,
 so significant changes in the implementation and API should be expected. Native
 addon developers are
-[encouraged to begin working with the API](/docs/guides/publishing-napi-modules/)
+[encouraged to begin working with the API](https://nodejs.org/docs/guides/publishing-napi-modules/)
 as soon as possible and to provide feedback that will be necessary to ensure
 that the new API meets the needs of the ecosystem.
 

pages/en/blog/vulnerability/march-2018-security-releases.md

@@ -31,7 +31,7 @@ OpenSSL 1.0.2o also contains a small number of code changes that are part of the
 
 ## Node.js Inspector DNS rebinding vulnerability (CVE-2018-7160)
 
-Node.js 6.x and later include a [debugger protocol](/docs/inspector/) (also known as "inspector") that can be activated by the `--inspect` and related command line flags. This debugger service was vulnerable to a [DNS rebinding attack](https://en.wikipedia.org/wiki/DNS_rebinding) which could be exploited to perform remote code execution.
+Node.js 6.x and later include a [debugger protocol](https://nodejs.org/docs/inspector/) (also known as "inspector") that can be activated by the `--inspect` and related command line flags. This debugger service was vulnerable to a [DNS rebinding attack](https://en.wikipedia.org/wiki/DNS_rebinding) which could be exploited to perform remote code execution.
 
 The attack was possible from malicious websites open in a web browser on the same computer, or another computer with network access to the computer running the Node.js process. A malicious website could use a DNS rebinding attack to trick the web browser to bypass [same-origin-policy](https://en.wikipedia.org/wiki/Same-origin_policy) checks and to allow HTTP connections to localhost or to hosts on the local network. If a Node.js process with the debug port active is running on localhost or on a host on the local network, the malicious website could connect to it as a debugger, and get full code execution access.
 

pages/en/docs/guides/diagnostics/index.md

@@ -15,8 +15,8 @@ root-cause their issues.
 
 This is the available set of diagnostics guides:
 
-- [Memory](/docs/guides/diagnostics/memory)
-- [Live Debugging](/docs/guides/diagnostics/live-debugging)
-- [Poor Performance](/docs/guides/diagnostics/poor-performance)
+- [Memory](https://nodejs.org/docs/guides/diagnostics/memory)
+- [Live Debugging](https://nodejs.org/docs/guides/diagnostics/live-debugging)
+- [Poor Performance](https://nodejs.org/docs/guides/diagnostics/poor-performance)
 
 [Diagnostics Working Group]: https://github.com/nodejs/diagnostics

pages/en/docs/guides/diagnostics/live-debugging/index.md

@@ -28,4 +28,4 @@ application executes for a certain trigger like an incoming HTTP request. They
 may also want to step through the code and control the execution as well as
 inspect what values variables hold in memory.
 
-- [Using Inspector](/docs/guides/diagnostics/live-debugging/using-inspector)
+- [Using Inspector](https://nodejs.org/docs/guides/diagnostics/live-debugging/using-inspector)

pages/en/docs/guides/diagnostics/memory/index.md

@@ -58,6 +58,6 @@ type of objects take and what variables are preventing them from being garbage
 collected. It can also help to know the allocation pattern of our program over
 time.
 
-- [Using Heap Profiler](/docs/guides/diagnostics/memory/using-heap-profiler/)
-- [Using Heap Snapshot](/docs/guides/diagnostics/memory/using-heap-snapshot/)
-- [GC Traces](/docs/guides/diagnostics/memory/using-gc-traces)
+- [Using Heap Profiler](https://nodejs.org/docs/guides/diagnostics/memory/using-heap-profiler/)
+- [Using Heap Snapshot](https://nodejs.org/docs/guides/diagnostics/memory/using-heap-snapshot/)
+- [GC Traces](https://nodejs.org/docs/guides/diagnostics/memory/using-gc-traces)

pages/en/docs/guides/diagnostics/poor-performance/index.md

@@ -32,5 +32,5 @@ the others. When we do this locally, we usually try to optimize our code.
 
 This document provides two simple ways to profile a Node.js application:
 
-- [Using V8 Sampling Profiler](/docs/guides/simple-profiling/)
-- [Using Linux Perf](/docs/guides/diagnostics/poor-performance/using-linux-perf)
+- [Using V8 Sampling Profiler](https://nodejs.org/docs/guides/simple-profiling/)
+- [Using Linux Perf](https://nodejs.org/docs/guides/diagnostics/poor-performance/using-linux-perf)

pages/en/docs/guides/diagnostics/poor-performance/using-linux-perf.md

@@ -72,11 +72,11 @@ visualization.
 
 ![Example nodejs flamegraph](https://user-images.githubusercontent.com/26234614/129488674-8fc80fd5-549e-4a80-8ce2-2ba6be20f8e8.png)
 
-To generate a flamegraph from this result, follow [this tutorial](/docs/guides/diagnostics-flamegraph/#create-a-flame-graph-with-system-perf-tools)
+To generate a flamegraph from this result, follow [this tutorial](https://nodejs.org/docs/guides/diagnostics-flamegraph/#create-a-flame-graph-with-system-perf-tools)
 from step 6.
 
 Because `perf` output is not a Node.js specific tool, it might have issues with how JavaScript code is optimized in
-Node.js. See [perf output issues](/docs/guides/diagnostics-flamegraph/#perf-output-issues) for a
+Node.js. See [perf output issues](https://nodejs.org/docs/guides/diagnostics-flamegraph/#perf-output-issues) for a
 futher reference.
 
 ## Useful Links

pages/en/docs/guides/index.md

@@ -7,21 +7,21 @@ layout: docs.hbs
 
 ## General
 
-- [Debugging - Getting Started](/docs/guides/debugging-getting-started/)
-- [Easy profiling for Node.js Applications](/docs/guides/simple-profiling/)
-- [Diagnostics - Flame Graphs](/docs/guides/diagnostics-flamegraph/)
-- [Diagnostics - User Journey](/docs/guides/diagnostics/)
-- [Security Best Practices](/docs/guides/security/)
+- [Debugging - Getting Started](https://nodejs.org/docs/guides/debugging-getting-started/)
+- [Easy profiling for Node.js Applications](https://nodejs.org/docs/guides/simple-profiling/)
+- [Diagnostics - Flame Graphs](https://nodejs.org/docs/guides/diagnostics-flamegraph/)
+- [Diagnostics - User Journey](https://nodejs.org/docs/guides/diagnostics/)
+- [Security Best Practices](https://nodejs.org/docs/guides/security/)
 
 ## Node.js core concepts
 
-- [The Node.js Event Loop, Timers, and `process.nextTick()`](/docs/guides/event-loop-timers-and-nexttick/)
-- [Don't Block the Event Loop (or the Worker Pool)](/docs/guides/dont-block-the-event-loop/)
+- [The Node.js Event Loop, Timers, and `process.nextTick()`](https://nodejs.org/docs/guides/event-loop-timers-and-nexttick/)
+- [Don't Block the Event Loop (or the Worker Pool)](https://nodejs.org/docs/guides/dont-block-the-event-loop/)
 
 ## Module-related guides
 
-- [Anatomy of an HTTP Transaction](/docs/guides/anatomy-of-an-http-transaction/)
-- [Working with Different Filesystems](/docs/guides/working-with-different-filesystems/)
-- [Backpressuring in Streams](/docs/guides/backpressuring-in-streams/)
-- [How to publish N-API package](/docs/guides/publishing-napi-modules/)
-- [ABI Stability](/docs/guides/abi-stability/)
+- [Anatomy of an HTTP Transaction](https://nodejs.org/docs/guides/anatomy-of-an-http-transaction/)
+- [Working with Different Filesystems](https://nodejs.org/docs/guides/working-with-different-filesystems/)
+- [Backpressuring in Streams](https://nodejs.org/docs/guides/backpressuring-in-streams/)
+- [How to publish N-API package](https://nodejs.org/docs/guides/publishing-napi-modules/)
+- [ABI Stability](https://nodejs.org/docs/guides/abi-stability/)

pages/en/learn/asynchronous-work/the-nodejs-event-emitter.md

@@ -8,7 +8,7 @@ authors: flaviocopes, MylesBorins, fhemberger, LaRuaNa, ahmadawais, ovflowd
 
 If you worked with JavaScript in the browser, you know how much of the interaction of the user is handled through events: mouse clicks, keyboard button presses, reacting to mouse movements, and so on.
 
-On the backend side, Node.js offers us the option to build a similar system using the [`events` module](/api/events/).
+On the backend side, Node.js offers us the option to build a similar system using the [`events` module](https://nodejs.org/api/events/).
 
 This module, in particular, offers the `EventEmitter` class, which we'll use to handle our events.
 
@@ -67,4 +67,4 @@ The EventEmitter object also exposes several other methods to interact with even
 - `removeListener()` / `off()`: remove an event listener from an event
 - `removeAllListeners()`: remove all listeners for an event
 
-You can read more about these methods in the [official documentation](/api/events/).
+You can read more about these methods in the [official documentation](https://nodejs.org/api/events/).

pages/en/learn/command-line/how-to-use-the-nodejs-repl.md

@@ -149,4 +149,4 @@ local.on('exit', () => {
 });
 ```
 
-You can read more about the REPL module in the [repl documentation](/api/repl/).
+You can read more about the REPL module in the [repl documentation](https://nodejs.org/api/repl/).

pages/en/learn/command-line/output-to-the-command-line-using-nodejs.md

@@ -8,7 +8,7 @@ authors: flaviocopes, potch, MylesBorins, fhemberger, LaRuaNa, amiller-gh, ahmad
 
 ### Basic output using the console module
 
-Node.js provides a [`console` module](/api/console/) which provides tons of very useful ways to interact with the command line.
+Node.js provides a [`console` module](https://nodejs.org/api/console/) which provides tons of very useful ways to interact with the command line.
 
 It is basically the same as the `console` object you find in the browser.
 

pages/en/learn/manipulating-files/nodejs-file-stats.md

@@ -6,7 +6,7 @@ authors: flaviocopes, ZYSzys, MylesBorins, fhemberger, LaRuaNa, ahmadawais, clea
 
 # Node.js file stats
 
-Every file comes with a set of details that we can inspect using Node.js. In particular, using the `stat()` method provided by the [`fs` module](/api/fs/).
+Every file comes with a set of details that we can inspect using Node.js. In particular, using the `stat()` method provided by the [`fs` module](https://nodejs.org/api/fs/).
 
 You call it passing a file path, and once Node.js gets the file details it will call the callback function you pass, with 2 parameters: an error message, and the file stats:
 
@@ -78,4 +78,4 @@ async function example() {
 example();
 ```
 
-You can read more about the `fs` module in the [official documentation](/api/fs/).
+You can read more about the `fs` module in the [official documentation](https://nodejs.org/api/fs/).

pages/en/learn/manipulating-files/working-with-file-descriptors-in-nodejs.md

@@ -78,4 +78,4 @@ async function example() {
 example();
 ```
 
-To see more details about the `fs/promises` module, please check [fs/promises API](/api/fs/#promise-example).
+To see more details about the `fs/promises` module, please check [fs/promises API](https://nodejs.org/api/fs/#promise-example).

pages/en/learn/manipulating-files/writing-files-with-nodejs.md

@@ -73,7 +73,7 @@ fs.writeFile('/Users/joe/test.txt', content, { flag: 'a+' }, err => {});
 | `a`  | This flag opens the file for **writing** and it also positions the stream at the **end** of the file                       |                  ✅                   |
 | `a+` | This flag opens the file for **reading** and **writing** and it also positions the stream at the **end** of the file       |                  ✅                   |
 
-- You can find more information about the flags in the [fs documentation](/api/fs/#file-system-flags).
+- You can find more information about the flags in the [fs documentation](https://nodejs.org/api/fs/#file-system-flags).
 
 ## Appending content to a file