5. Develop locally with WranglerWhen using wrangler dev to develop locally, wrangler will default to using a local version of KV to avoid interfering with any of your live production data in KV. This means that reading keys that you have not written locally will return null.To have wrangler dev connect to your Workers KV namespace running on Cloudflare’s global network, call wrangler dev --remote instead.While in your project directory, test your KV locally by running:wrangler devWhen you run wrangler dev, Wrangler will give you a URL (usually a localhost:8787) to review your Worker. After you visit the URL Wrangler provides, you will see your value printed on the browser.
5. Develop locally with WranglerWhen using wrangler dev to develop locally, wrangler will default to using a local version of KV to avoid interfering with any of your live production data in KV. This means that reading keys that you have not written locally will return null.To have wrangler dev connect to your Workers KV namespace running on Cloudflare’s global network, call wrangler dev --remote instead.While in your project directory, test your KV locally by running:wrangler devWhen you run wrangler dev, Wrangler will give you a URL (usually a localhost:8787) to review your Worker. After you visit the URL Wrangler provides, you will see your value printed on the browser.
But this is wrong:
wrangler pages dev ./public --kv=testNS --remoteX [ERROR] Unknown argument: remotewrangler pages dev [directory] [-- command..]
wrangler pages dev ./public --kv=testNS --remoteX [ERROR] Unknown argument: remotewrangler pages dev [directory] [-- command..]