Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

Jump to bottom

vercel-kv driver #218

Closed
pi0 opened this issue May 5, 2023 · 0 comments
Closed

vercel-kv driver #218

pi0 opened this issue May 5, 2023 · 0 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@pi0
Copy link
Member

pi0 commented May 5, 2023 •
edited
Loading

Initial support for vercel-kv driver added in #213.

The platform feature itself is in beta, please check Vercel KV Limits for more info.

While testing and adding tests, I discovered some issues:

  • For node.js environments, fetch polyfill is required (Node 16). We might need to either document it or add polyfill to driver or upstream. (nuxt and nitro already polyfill fetch)
  • Driver import (even if not used!) fails since @vercel/kv requires KV_REST_API_URL and KV_REST_API_TOKEN for its default export. (it works when bundled only with rollup/nitro/nuxt/etc). Needs more investigation. Might be only issue with vitest.
@pi0 pi0 mentioned this issue May 5, 2023
Merged
@pi0 pi0 added bug Something isn't working documentation Improvements or additions to documentation labels May 5, 2023
@pi0 pi0 changed the title Issues with vercel-kv driver vercel-kv driver May 5, 2023
@pi0 pi0 closed this as completed Jul 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pi0