fix: lower engines #1006
Merged
fix: lower engines #1006
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
Vercel uses aws lambda versions in it's build process. Currently the latest v14 version used by aws is v14.19.0. By raising to `>=14.19.1` you prevent vercel builds from succeeding (until that cap is bumped). See here for aws lambda version: https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platform-history-nodejs.html
✅ Deploy Preview for vitest-dev ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
antfu
changed the title
|
I think this fix should be applied to the I tried to deploy a site to vercel and got the following error: |
Closed
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.
Vercel uses aws lambda versions in it's build process. Currently the latest v14 version used by aws is v14.19.0. By raising to
>=14.19.1you prevent vercel builds from succeeding (until that cap is bumped).See here for aws lambda version: https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platform-history-nodejs.html
Note that I didn't touch the renvoate config. You likely don't want the engines version pinned to the latest patch version.