# Next.js

Endless Lifecycle Support (ELS) for Next.js from TuxCare provides security fixes for Next.js versions that have reached their end of life. This allows you to continue running Next.js applications without vulnerability concerns, even after official support has ended.

# Supported Next.js Versions

• Next.js 12.3.7, 13.5.11, 14.2.35, 16.0.6

# Connection to ELS for Next.js Library

This guide outlines the steps needed to integrate the TuxCare ELS for the Next.js library.

# Step 1: Get Token

You need a token in order to use TuxCare ELS Next.js library. Anonymous access is disabled. To receive the token, please contact sales@tuxcare.com.

# Step 2: Set Up ELS for Next.js

TuxCare provides ELS for Next.js as an NPM package, hosted on a secure internal registry. Follow the steps below to add it to your project and get started.

1. Navigate to the root directory of your Next.js project.

2. Create a .npmrc file or update it if it already exists.

   Example:

   my-nextjs-project/
   ├── node_modules/
   ├── package.json
   ├── .npmrc         ⚠️ ← Create it here
   └── package-lock.json
   

3. Use an editor of your choice (e.g., VS Code) to add the following registry address line:

   registry=https://registry.npmjs.org/
   @els-js:registry=https://nexus.repo.tuxcare.com/repository/els-js/
   //nexus.repo.tuxcare.com/repository/els-js/:_auth=${TOKEN}
   

   Replace ${TOKEN} with the token you received from sales@tuxcare.com.

4. Update your package.json file to replace your Next.js dependencies with the TuxCare packages. You can do this in two ways:

   • Option 1: Manual update

     Manually update your package.json file by replacing your Next.js dependencies with the TuxCare packages. This method gives you full control over which packages to update.

     Choose Next.js version: next 12.3.7next 13.5.11next 14.2.35next 16.0.6

     "dependencies": {
       "next": "npm:@els-js/next@>=12.3.7-tuxcare.1"
     },
     "overrides": {
       "next@12.3.7": "npm:@els-js/next@>=12.3.7-tuxcare.1"
     }
     

   • Option 2: TuxCare Patcher (Automated)

     Install the Patcher globally and run it. The TuxCare Patcher automatically detects the Next.js version in your package.json and updates your dependencies and overrides to use the corresponding TuxCare @els-js/* packages.

     npm install -g @els-js/tuxcare-patcher --userconfig ./.npmrc
     tuxcare-patch-js
     

     The patcher will update your package.json, for example, from:

     "dependencies": {
       "next": "^12.3.7"
     }
     

     to:

     "dependencies": {
       "next": "npm:@els-js/next@>=12.3.7-tuxcare.1"
     },
     "overrides": {
       "next@12.3.7": "npm:@els-js/next@>=12.3.7-tuxcare.1"
     }
     

5. You need to remove the node_modules directory and the package-lock.json file, and also clear the npm cache before installing the patched packages. Use the following commands:

   rm -rf node_modules package-lock.json && npm cache clean --force
   

6. Run the following command to install the ELS version of the Next.js library (token for the TuxCare repository will be automatically picked up from your .npmrc file):

   npm install
   

# Step 3: Verify Installation

1. To confirm the TuxCare Next.js library is set up correctly, use npm to list the project's dependencies:

   npm list
   

2. After reviewing the dependencies, run your application to ensure everything works correctly.

The npm tool should be able to identify and resolve dependencies from the TuxCare ELS for Next.js repository.

# Vulnerability Exploitability eXchange (VEX)

VEX is a machine-readable format that tells you if a known vulnerability is actually exploitable in your product. It reduces false positives, helps prioritize real risks.

TuxCare provides VEX for Next.js ELS versions: security.tuxcare.com/vex/cyclonedx/els_lang_javascript/next/.

# How to Upgrade to a Newer Version of TuxCare Packages

If you have already installed a package with a tuxcare.1 suffix and want to upgrade to a newer release (for example, tuxcare.3), remove node_modules, clear the npm cache to avoid conflicts, and then run the installation command:

rm -rf node_modules package-lock.json && npm cache clean --force
npm install

# Resolved CVEs

Fixes for the following vulnerabilities are available in ELS for Next.js from TuxCare versions:

If you are interested in the TuxCare Endless Lifecycle Support, contact sales@tuxcare.com.