chore: node 18 upgrade #111
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In response to the evolving landscape of Node.js development and to ensure our project remains robust and up-to-date, this pull request (PR) addresses a critical update. As of late, Node.js version 16 has reached the end of its official support lifecycle. To align our project with the latest industry standards and security patches, we are proactively upgrading our Node.js environment from version 16 to the latest stable release, version 18.
This upgrade carries significant advantages that will directly benefit our project's performance, stability, and security. Node.js 18 introduces a host of new features, optimizations, and improvements that have the potential to enhance both our development experience and the final user-facing product.
Motivation and Context
One primary motivation behind this upgrade is to ensure that our project remains secure and protected against emerging vulnerabilities. With version 16 no longer receiving security updates, continuing to use it poses a potential risk to our application's integrity. By migrating to Node.js 18, we can leverage the latest security patches and fixes, bolstering the resilience of our codebase.
Changes:
Several places where node 16 was used including dokerfiles and package(-lock).json