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
Following the docs on Vercel (https://vercel.com/docs/runtimes#official-runtimes/node-js) the Node runtimes first use the req/res handler style and support changes to AWS style with configuration, eg: NODEJS_AWS_HANDLER_NAME.
NODEJS_AWS_HANDLER_NAME
It would be nice if now-deno supports the same APIs style.
now-deno
The text was updated successfully, but these errors were encountered:
I'd like to work on this, but I need to learn how now-deno works internally. 🤔
Sorry, something went wrong.
Until I know how this builder works, here's a wrapper to create @vercel/node like functions: https://github.com/grikomsn/deno-create-now-fn
@vercel/node
@grikomsn If you want you can add this code to this repo and document it in the README :-)
I'm still new to Vercel builders. Any pointers on where can I add/modify parts of the code?
No branches or pull requests
Following the docs on Vercel (https://vercel.com/docs/runtimes#official-runtimes/node-js) the Node runtimes first use the req/res handler style and support changes to AWS style with configuration, eg:
NODEJS_AWS_HANDLER_NAME
.It would be nice if
now-deno
supports the same APIs style.The text was updated successfully, but these errors were encountered: