We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
Deploying the template on vercel results in failed builds due to in invalid runtime for Vercel Serverless Functions.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Build should succeed when adding a sample post to the content collection per the template instructions.
Which versions of Sanity are you using?
Run sanity versions in the terminal and copy-paste the result here.
sanity versions
What operating system are you using?
@sanity/cli (global) 3.17.0 (latest: 3.35.0) @sanity/astro 1.3.0 (latest: 3.0.0) @sanity/image-url 1.0.2 (up to date) @sanity/types 3.17.0 (latest: 3.35.0) @sanity/vision 3.17.0 (latest: 3.35.0) sanity 3.17.0 (latest: 3.35.0)
Which versions of Node.js / npm are you running?
10.2.4 v18.19.1
** Proposed Solution **
This issue resolved for me by updating the package.json to have a more current version of node in the engines section.
package.json
engines
"engines": { "node": "18" }
The text was updated successfully, but these errors were encountered:
I'm also getting this error but the proposed solution did not fix it for me
Sorry, something went wrong.
No branches or pull requests
Describe the bug
Deploying the template on vercel results in failed builds due to in invalid runtime for Vercel Serverless Functions.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Build should succeed when adding a sample post to the content collection per the template instructions.
Which versions of Sanity are you using?
Run
sanity versions
in the terminal and copy-paste the result here.What operating system are you using?
Which versions of Node.js / npm are you running?
** Proposed Solution **
This issue resolved for me by updating the
package.json
to have a more current version of node in theengines
section.The text was updated successfully, but these errors were encountered: