-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(vercel): maxDuration config #8867
Conversation
🦋 Changeset detectedLatest commit: 7085f7f The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
runtime: getRuntime(), | ||
handler, | ||
launcherType: 'Nodejs', | ||
maxDuration, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the new part. Commenting for quick visibility.
Relevant Vercel docs: https://vercel.com/docs/build-output-api/v3/primitives#base-config.
It would be great if we can find out what's the maximum allowed, so we can throw an error early. Vercel documentation doesn't mention it, I see what I can do. |
Yes, it is 900s for enterprise customers. Although, I'm not sure if custom contracts can allow longer. https://vercel.com/docs/functions/serverless-functions/runtimes#maxduration |
06daf3c
to
0eb004e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Left a couple of suggestions! 🙌
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Co-authored-by: Sarah Rainsberger <sarah@rainsberger.ca>
Changes
Testing
Added a fixture and test that
.vc-config.json
has the expected field.Docs
Added a section to the README.