fix: update Vercel function handler

[fox1t]

In this PR:

• fixes Vercel function handler

Issues reference:

• closes Consider removing @vercel/node from the dependencies #154
• closes Current state of main branch is not deployable to vercel. #159

Checklist:

• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

• Have you lint your code with pnpm lint locally prior to submission?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran build with pnpm build of your changes locally?
• Have you successfully ran tests with pnpm test of your changes locally?
• Have you commit using Conventional Commits?

[render]

Your Render PR Server URL is https://turborepo-remote-cache-pr-222.onrender.com.

Follow its progress at https://dashboard.render.com/web/srv-ck703988elhc73ao09q0.

[socket-security]

New dependencies detected. Learn more about Socket for GitHub ↗︎

Packages	Version	New capabilities	Transitives	Size	Publisher
typescript	5.2.2	None	+0	40.6 MB	typescript-bot

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Issue	Package	Version	Note	Source
Chronological version anomaly	typescript	5.2.2	Previous Chronological: typescript@5.3.0-dev.20230824 (8/24/2023, 7:16:04 AM) Previous Semver: typescript@5.2.1-rc (8/9/2023, 6:02:32 PM)	@commitlint/cli@17.7.1, @commitlint/prompt@17.7.1, @ducktors/tsconfig@1.0.0 via package.json package.json

Next steps

What is a chronological version anomaly?

Semantic versions published out of chronological order.

This could either indicate dependency confusion or a patched vulnerability.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of package-name@version specifiers. e.g. @SocketSecurity ignore foo@1.0.0 bar@* or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore typescript@5.2.2

[matteovivona]

🎉 This PR is included in version 2.0.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀