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.

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

[Bug]: ReferenceError: caches is not defined #652

Closed
inverted-capital opened this issue Apr 15, 2024 · 3 comments
Closed

[Bug]: ReferenceError: caches is not defined #652

inverted-capital opened this issue Apr 15, 2024 · 3 comments

Comments

@inverted-capital
Copy link

Problem description

The beta features for web caches isn't working for me. I know it's beta, but its so good - what do I need to do to access it ?

My isolate was in australia: gcp-australia-southeast1

Steps to reproduce

Deploy any code that tries to access the caches global:

const cache = await caches.open('bart')

Deno.serve((req: Request) => new Response("Hello World"));

Expected behavior

Docs say its there - plz be there

Environment

No response

Possible solution

No response

Additional context

No response

@inverted-capital
Copy link
Author

Original issue seems here: #74

@danopia
Copy link

danopia commented May 10, 2024

I'm also looking for this feature for my AWS API codegen (first in a PR and then in a simple public playground). This API would really speed up and also simplify my Deno Deploy setup (a good combination!), I would love to give it a spin. Currently I am using an S3 bucket for a cache which means that other continents have increased latency.

I suppose the docs landed before the feature itself..

@inverted-capital
Copy link
Author

This available for me now. Docs say it is in closed beta. Hopefully we all get it real soon.

https://docs.deno.com/deploy/manual/edge-cache/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants