From 7b6e336bc58790f1006cd00adcd5a27988e6d62b Mon Sep 17 00:00:00 2001
From: Toru Kobayashi <koba0004@gmail.com>
Date: Thu, 20 Apr 2023 00:16:37 +0900
Subject: [PATCH] docs: fix minimum Node.js version to `14.18.0` (#48545)

fixes #42729

According to #42729, the minimum Node.js version of Next is `14.18.0`,
but some docs say `14.6.0`, and it's error-prone.
https://github.com/vercel/next.js/issues/42729#issuecomment-1309947579
pointed out it's a bug rather than wrong documentation.

But Node v14 is going to be EOF this month, so Next will update the
minimum version in the next major release.
https://github.com/nodejs/release#release-schedule

So I feel it's enough to only fix the documentation rather than fixing
the implementation to work with 14.6.0 as a temporary fix.


<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation or adding/fixing Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md



## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

---------

Co-authored-by: Steven <steven@ceriously.com>
---
 docs/getting-started.md               | 2 +-
 docs/upgrading.md                     | 2 +-
 package.json                          | 2 +-
 packages/create-next-app/package.json | 2 +-
 packages/next/package.json            | 2 +-
 packages/next/taskfile-swc.js         | 2 +-
 6 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/getting-started.md b/docs/getting-started.md
index da19febc66eb..f972b5544579 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -14,7 +14,7 @@ If you have questions about anything related to Next.js, you're always welcome t
 
 #### System Requirements
 
-- [Node.js 14.6.0](https://nodejs.org/) or newer
+- [Node.js 14.18.0](https://nodejs.org/) or newer
 - MacOS, Windows (including WSL), and Linux are supported
 
 ## Automatic Setup
diff --git a/docs/upgrading.md b/docs/upgrading.md
index 69596c4b4f35..63ebdd0231d3 100644
--- a/docs/upgrading.md
+++ b/docs/upgrading.md
@@ -19,7 +19,7 @@ pnpm up next react react-dom eslint-config-next --latest
 ### v13 Summary
 
 - The [Supported Browsers](/docs/basic-features/supported-browsers-features.md) have been changed to drop Internet Explorer and target modern browsers.
-- The minimum Node.js version has been bumped from 12.22.0 to 14.6.0, since 12.x has reached end-of-life.
+- The minimum Node.js version has been bumped from 12.22.0 to 14.18.0, since 12.x has reached end-of-life.
 - The minimum React version has been bumped from 17.0.2 to 18.2.0.
 - The `swcMinify` configuration property was changed from `false` to `true`. See [Next.js Compiler](/docs/advanced-features/compiler.md) for more info.
 - The `next/image` import was renamed to `next/legacy/image`. The `next/future/image` import was renamed to `next/image`. A [codemod is available](/docs/advanced-features/codemods.md#next-image-to-legacy-image) to safely and automatically rename your imports.
diff --git a/package.json b/package.json
index c431aa60de36..80464d31fabf 100644
--- a/package.json
+++ b/package.json
@@ -243,7 +243,7 @@
     "@babel/traverse": "7.18.0"
   },
   "engines": {
-    "node": ">=14.6.0"
+    "node": ">=14.18.0"
   },
   "packageManager": "pnpm@7.24.3"
 }
diff --git a/packages/create-next-app/package.json b/packages/create-next-app/package.json
index 0d3ef200b205..eb001ee6e3b9 100644
--- a/packages/create-next-app/package.json
+++ b/packages/create-next-app/package.json
@@ -55,6 +55,6 @@
     "validate-npm-package-name": "3.0.0"
   },
   "engines": {
-    "node": ">=14.6.0"
+    "node": ">=14.18.0"
   }
 }
diff --git a/packages/next/package.json b/packages/next/package.json
index 9597761cd08f..5d099afe0fc4 100644
--- a/packages/next/package.json
+++ b/packages/next/package.json
@@ -315,6 +315,6 @@
     "caniuse-lite": "1.0.30001406"
   },
   "engines": {
-    "node": ">=14.6.0"
+    "node": ">=14.18.0"
   }
 }
diff --git a/packages/next/taskfile-swc.js b/packages/next/taskfile-swc.js
index d293db987c8b..4b95d175fca9 100644
--- a/packages/next/taskfile-swc.js
+++ b/packages/next/taskfile-swc.js
@@ -66,7 +66,7 @@ module.exports = function (task) {
         env: {
           targets: {
             // follow the version defined in packages/next/package.json#engine
-            node: '14.6.0',
+            node: '14.18.0',
           },
         },
         jsc: {