Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Node.js (v16 reached end of life) Version and Next.js for Safety & to Leverage Modern Features #537

Closed
ve-varun-sharma opened this issue Aug 17, 2024 · 2 comments

Comments

@ve-varun-sharma
Copy link
Contributor

Description

The current documentation for the open-sourced Next.js app for Railway.app is using Node.js version 16.0.0 Node.js version 16 reached its End-of-Life (EOL) on September 2023, leaving the project vulnerable to security risks and missing out on performance improvements in newer versions.

This issue highlights the need to upgrade the following aspects of the project:

  • Node.js: Update to a Long-Term Support (LTS) version like Node.js 18.x or the latest LTS version available at the time of upgrade.
  • Next.js: Due to the Node.js version bump, it would be possible to upgrade Next.js to version 14 or the latest stable version, allowing the project to benefit from performance enhancements and new features.

Benefits of Upgrading:

  • Improved Security: Utilizing a supported Node.js version ensures access to security patches and reduces the risk of vulnerabilities.
  • Enhanced Performance: Upgrading Next.js can offer improved performance and access to new features in the latest version.
  • Modern Development: Maintaining compatibility with current Node.js and Next.js versions allows for safer and more reliable dependency upgrades.

Proposed Solution:

  • Update package.json to specify the latest compatible LTS version of Node.js and the desired Next.js version. This also ensures the app deployed on railway infrastructure use the right node version
  • Update any other dependencies in the project that require Node.js version 18 or higher as needed.
  • Test the application thoroughly after the upgrade to ensure everything functions as intended.

Additional Considerations:

  • This issue focuses on upgrading Node.js and Next.js versions. It's recommended to review the compatibility of all core project dependencies after the Node.js upgrade.
  • We can consider creating a separate pull request for each upgrading the node version and then the next version separately.

Meme

image

@ndneighbor
Copy link
Contributor

Closing as both PRs have been merged. Cheers!

@ve-varun-sharma
Copy link
Contributor Author

Closing as both PRs have been merged. Cheers!

Amazing!!! 🍻 :) Thanks for the speedy resolution on this! 😲 ❤️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants