Vercel dev CLI using old typescript version

[nipunn1313]

Hi,

In my project, I'm running vercel dev from the CLI to run a serverless function. When my serverless function is invoked, it appears to run typescript on my serverless function using an old version of typescript.

Example error:

node_modules/convex/dist/esm/browser/browser.d.ts:174:39 - error TS2304: Cannot find name 'Awaited'.

174 (...args: Parameters): Promise<Awaited<ReturnType>>;
Awaited was introduced in typescript 4.5.

My local package.json references typescript 4.7 and running npx tsc locally passes.

EDIT:
While debugging I found this:

➜  4b-external-functions-vercel git:(main) ✗ for t in `find . -name tsc`; do echo $t ; $t --version; done
./node_modules/.bin/tsc
Version 4.7.4
./node_modules/typescript/bin/tsc
Version 4.7.4
./node_modules/@vercel/node/node_modules/.bin/tsc
Version 4.3.4
./node_modules/@vercel/node/node_modules/typescript/bin/tsc
Version 4.3.4

So I'm suspicious that @vercel/node is shipping with an old version of typescript and then choosing that version over the one I have locally installed from my package.json.

[swarnava]

Have you tried removing package-lock.json and then deploy?

[nipunn1313]

Hi Amy! Thanks for taking a look.

I don't think upgrading typescript@4.3.4 is the ideal fix (though I wouldn't be against it independently).

IMO, Vercel should either

• Run the version of typescript that is in the package.json of MY project. Not the one bundled with vercel.
• Stop running typescript dynamically on api/ functions at the time they are called

open to being convinced otherwise.
Upgrading typescript still means there is a discrepancy between the typescript version specified by project owner in package.json and the one being run by vercel.

[amyegan]

Thanks for clarifying! I updated the issue summary

[vxna]

Having the same problem using the got package with vc dev.
@amyegan I think it's worth converting this discussion thread into an issue 👍

ref: sindresorhus/got#2164 (comment)

[amyegan]

Thanks for sharing this info @vxna. You can find the issue created from the original post here #8680

[martin-dimi]

@vxna I'm having the same issue. Did you manage to fix this?

[netgfx]

I think my issue is related to this as well I get /bin/sh: tsc: command not found when trying to build types of my repository. The failing command is: "build:types": "tsc --declaration --emitDeclarationOnly",
What can be done about this? I have included typescript as a devDependency 4.9.2

[AnimeshTimsina]

how did you solve this?

[netgfx]

I didn't. I set up vercel to pull from repository instead and then it wasn't having any issues. The issue was caused when I tried to deploy from Codesanbox through vercel