Update package.json to fix node v22.12 error on serverless #1845
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
The error is the same as stated here serverless/serverless#12936 as the version target as dependency for the serverless-offline v13 is serverless ^3.2 the fixing update is not enforced. Being nodejs22.x a supported runtime I think the version should be changed to fix this here also.
zoellner
added a commit
to BrightCrowd/serverless-offline
that referenced
this pull request
Jun 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
The error is the same as stated here serverless/serverless#12936 as the version target as dependency for the serverless-offline v13 is serverless ^3.2 the fixing update is not enforced.
Being nodejs22.x a supported runtime I think the version should be changed to fix this here also.
Motivation and Context
Fix #1844
How Has This Been Tested?
Adding the following line on devDependecies and running npm install does so the problem does not occur anymore and serverless offline can be started.