there is nothing to do with my deploy, but only local-dev envirnment.
env:
package.json:
{
"name": "vercel-serverless",
"version": "1.0.1",
"description": "",
"main": "index.js",
"scripts": {
"vercel": "vercel dev",
"postinstall": "prisma generate"
},
"author": "",
"license": "ISC",
"devDependencies": {
"@fastify/type-provider-typebox": "^5.0.1",
"@types/node": "^18.0.0",
"@vercel/node": "^2.6.1",
"prisma": "^5.7.1",
"ts-node": "10.9.2",
"typescript": "4.9.5"
},
"dependencies": {
"@fastify/autoload": "^5.0.0",
"@fastify/sensible": "^5.0.0",
"@prisma/client": "^5.22.0",
"dotenv": "^16.0.3",
"fastify": "^4.9.2",
"fastify-cli": "^5.5.1",
"fastify-plugin": "^4.0.0"
},
"overrides": {
"@vercel/node": {
"ts-node": "10.9.2",
"typescript": "5.6.2"
}
}
}
pawlean
(Pauline P. Narvas)
2
Hi, @xhfkindergarten! Welcome to the Vercel Community 
Based on the specific errors you’re seeing with Fastify’s type definitions, this is likely a TypeScript configuration issue.
You can try running the development server with the --ignore-ts-errors
flag as a temporary solution:
vercel dev --ignore-ts-errorsvercel dev --ignore-ts-errors
But it might want to check your package versions to ensure compatibility:
npm list fastify @types/node typescriptnpm list fastify @types/node typescript
Make sure your Fastify version and TypeScript version are compatible. You might want to update to the latest stable versions:
npm install fastify@latest typescript@latest @types/node@latestnpm install fastify@latest typescript@latest @types/node@latest
Let us know how you get on!
Thanks, pawlean. actually my dependencies were already latest.
here is a minimal demo that can reproduct this.
system
(system)
Closed
4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.