The Cloudflare KV namespace remains unbound

Question

The Cloudflare KV namespace remains unbound

After running wrangler dev, it appears that Worker KV is not being bound properly:

ERROR in /src/handler.ts
./src/handler.ts 16:8-17
[tsl] ERROR in /src/handler.ts(16,9)
      TS2304: Cannot find name 'generalKV'.

This is the content of handler.ts:

async function postHandler(request: Request): Promise<Response> {
  let content = JSON.stringify(await request.json());
  await generalKV.put([Date.now().toString()], JSON.stringify(content));
  return new Response(content);
}

Contents of wrangler.toml:

name = "general-assignment"
type = "javascript"
account_id = "<id>"
workers_dev = true
compatibility_date = "2021-11-01"
kv_namespaces = [ 
    { binding = "generalKV", id = "<id>", preview_id = "<id>" }
]

Some have suggested changing kv_namespaces to kv-namespaces, but this solution did not work for me. Please advise if there are any other steps I may have missed.

javascript typescript cloudflare cloudflare-workers

Answer 1

Answer №1

For those who discover this question through Google and are using Wrangler v2, encountering the following error:

Uncaught (in promise) ReferenceError: MY_KV is not defined

The tutorials and guides often overlook a crucial second parameter (and a third parameter). This second parameter represents the environment. To successfully utilize and connect to kv, follow these steps:

# Initialize the KV namespaces
wrangler kv:namespace create "MY_KV" &&\
wrangler kv:namespace create "MY_KV" --preview

wrangler will give an error if the preview KV namespace is missing, hence it's recommended to create both. Afterward, add an entry for kv_namespaces array and duplicate the preview_id in the default (dev) section (indicated as yyyy below).

# wrangler.toml
name = "worker"
main = "src/index.js"
compatibility_date = "2022-04-14"
account_id = "...."
workers_dev = true

routes = [
    "exmample.com/*"
]

# Duplicate preview_id to id
kv_namespaces = [
    { binding = "MY_KV", preview_id = "yyyy", id = "yyyy" }
]

# Execute `wrangler publish --env production` when ready
[env.production]
kv_namespaces = [
    { binding = "MY_KV", id = "xxxx" }
]

You can now access kv bindings like this:

# index.js
export default {
  async fetch(request, env) {
  ...
  const someKV = env.MY_KV.get("some-key");
  ...
  }

Answer 2

For those who discover this question through Google and are using Wrangler v2, encountering the following error:

Uncaught (in promise) ReferenceError: MY_KV is not defined

The tutorials and guides often overlook a crucial second parameter (and a third parameter). This second parameter represents the environment. To successfully utilize and connect to kv, follow these steps:

# Initialize the KV namespaces
wrangler kv:namespace create "MY_KV" &&\
wrangler kv:namespace create "MY_KV" --preview

wrangler will give an error if the preview KV namespace is missing, hence it's recommended to create both. Afterward, add an entry for kv_namespaces array and duplicate the preview_id in the default (dev) section (indicated as yyyy below).

# wrangler.toml
name = "worker"
main = "src/index.js"
compatibility_date = "2022-04-14"
account_id = "...."
workers_dev = true

routes = [
    "exmample.com/*"
]

# Duplicate preview_id to id
kv_namespaces = [
    { binding = "MY_KV", preview_id = "yyyy", id = "yyyy" }
]

# Execute `wrangler publish --env production` when ready
[env.production]
kv_namespaces = [
    { binding = "MY_KV", id = "xxxx" }
]

You can now access kv bindings like this:

# index.js
export default {
  async fetch(request, env) {
  ...
  const someKV = env.MY_KV.get("some-key");
  ...
  }

Answer 3

Answer №2

Have you manually established the KV namespace on Cloudflare already? I don't think it automatically generates them based on the worker binding setup (at least not yet).

Instructions for creating via Wrangler can be found here -

https://example.com/create-kv-namespace

Answer 4

Have you manually established the KV namespace on Cloudflare already? I don't think it automatically generates them based on the worker binding setup (at least not yet).

Instructions for creating via Wrangler can be found here -

https://example.com/create-kv-namespace

The Cloudflare KV namespace remains unbound

Answer №1

Answer №2

Similar questions

Error in Deno pooling map server due to unhandled AggregateError

Transferring information from RSC to a nested child component using the Next.js application router

What causes the immediate firing of the DOM callback in Angular 1.2.9?

Inconsistencies in Executing JavaScript Methods Between Mobile Safari and Android Chrome

Transforming numerical figures into written form within a specified range: A step-by-step guide

Is the this.props.onChange method called within the render function?

What could be causing the "function undefined" error in my HTML document?

Using the .ajax() function with jQuery to retrieve data and then using .find() on that data

Efficiently handling jsonwebtoken errors in node and express

Loop through the numbers entered into a table field

Updating the div#content dynamically with Jquery without the need to refresh the page

How to retrieve an element using a dynamically generated class name in Vue.js

Express Concurrency: Managing Multiple Tasks Simultaneously

What is the best way to implement sorting in a table using react virtualized?

Is it possible to include additional information when creating a subscription for a customer on Stripe using Node.js

Editing the content of a div in real-time by dynamically updating the innerHTML

Exporting a function from Vue's `<script setup>` is similar to exporting from a module

What is the best way to reset form after submission in Next.js?

NGRX 8 reducer now outputting an Object rather than an Array

Interactive radio button that only registers the most recent click