MOL-29317: set Node 18 as default and upgrade eslint-plugin-jsdoc #55
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
this commit sets Node 18 as the default engine and upgrades the eslint-plugin-jsdoc package. This is to avoid errors that arise due to incompatibilities with older versions of Node. BREAKING CHANGE: projects using older versions of Node may experience issues and will need to upgrade to Node 18. The eslint-plugin-jsdoc package upgrade may also introduce breaking changes that require updates to the existing codebase. Issues: MOL-29317
carlosvillademor
approved these changes
Apr 17, 2024
|
This PR is now redundant as its purpose has been fulfilled by another PR, which can be found here: #54 |
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.
this commit sets Node 18 as the default engine and upgrades the eslint-plugin-jsdoc package. This is to avoid errors that arise due to incompatibilities with older versions of Node.
BREAKING CHANGE: projects using older versions of Node may experience issues and will need to upgrade to Node 18. The eslint-plugin-jsdoc package upgrade may also introduce breaking changes that require updates to the existing codebase.
Issues: MOL-29317