Added support for node version 22 #4805
Open
Conversation
This file contains hidden or 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
|
thanks! can you remove the |
Maxiweb
force-pushed
the
feature/node-upgrade-22
branch
from
a2ea55d to
89cdd5a
Compare
|
thanks @HenryHengZJ done :) |
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
Changes
Updated package.json to set the Node.js engine to version 22.
Modified the GitHub Actions workflow (main.yml) to run on Node.js v22.
Regenerated pnpm-lock.yaml to reflect dependency resolution under Node.js 22.
Purpose
These changes ensure that Flowise is compatible with and tested against the latest Node.js version (v22), helping to future-proof the project and align with the latest performance and security improvements.