hey all, anyone have any experience with using durable objects from within next routes, locally? it

hey all, anyone have any experience with using durable objects from within next routes, locally? it doesnt seem like my DO is starting up right, when i attempt to get an id/stub everything is just undefined... I have something like this:

export async function GET(request: NextRequest) {
  const context = getRequestContext();

  let id = context.env.RATE_LIMITER.idFromName(new URL(request.url).pathname);
  const stub = context.env.RATE_LIMITER.get(id);

  console.log({ id, stub });

  return stub.fetch(request);
}

export async function GET(request: NextRequest) {
  const context = getRequestContext();

  let id = context.env.RATE_LIMITER.idFromName(new URL(request.url).pathname);
  const stub = context.env.RATE_LIMITER.get(id);

  console.log({ id, stub });

  return stub.fetch(request);
}

export async function GET(request: NextRequest) {
  const context = getRequestContext();

  let id = context.env.RATE_LIMITER.idFromName(new URL(request.url).pathname);
  const stub = context.env.RATE_LIMITER.get(id);

  console.log({ id, stub });

  return stub.fetch(request);
}

export async function GET(request: NextRequest) {
  const context = getRequestContext();

  let id = context.env.RATE_LIMITER.idFromName(new URL(request.url).pathname);
  const stub = context.env.RATE_LIMITER.get(id);

  console.log({ id, stub });

  return stub.fetch(request);
}

which is just giving me:

{
  id: constructor { name: undefined },
  stub: constructor { name: undefined, id: undefined }
}
 ⨯ Error [TypeError]: Failed to parse URL from [object Request]

{
  id: constructor { name: undefined },
  stub: constructor { name: undefined, id: undefined }
}
 ⨯ Error [TypeError]: Failed to parse URL from [object Request]

{
  id: constructor { name: undefined },
  stub: constructor { name: undefined, id: undefined }
}
 ⨯ Error [TypeError]: Failed to parse URL from [object Request]

{
  id: constructor { name: undefined },
  stub: constructor { name: undefined, id: undefined }
}
 ⨯ Error [TypeError]: Failed to parse URL from [object Request]

MattOP•4/13/24, 5:25 PM

if I run the DO seperately with wrangler dev ./thedo.tswrangler dev ./thedo.ts i can hit the DO directly in the browser without any issues

Tthanhle try to use cache:no-store instead.

faye•4/13/24, 10:40 PM

This does not work FYI

Ffaye Heyo! It seems that using 14.2.1 (so far I know), I am suddenly getting a weird...

James•4/14/24, 11:54 AM

are you able to share a reproduction? I wasn't having much luck trying to reproduce it

faye•4/14/24, 11:54 AM

Let me see

JJames are you able to share a reproduction? I wasn't having much luck trying to reprod...

faye•4/14/24, 11:57 AM

Might it be because the GET is in a server action?

faye•4/14/24, 11:58 AM

Because it's as simple as:

faye•4/14/24, 11:59 AM

(the cache: 'no-cache'cache: 'no-cache' part)

James•4/14/24, 1:42 PM

Hmm I haven't tried reproducing it in a server action before, will see if I have some time this evening to try it out

luna•4/15/24, 12:36 PM

trying to use @cloudflare/pages-plugin-vercel-og/api@cloudflare/pages-plugin-vercel-og/api and im getting a load of errors like so.

 ⨯ ./node_modules/@cloudflare/pages-plugin-vercel-og/dist/src/api/noto-sans-v27-latin-regular.ttf.bin
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

 ⨯ ./node_modules/@cloudflare/pages-plugin-vercel-og/dist/src/api/noto-sans-v27-latin-regular.ttf.bin
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Pat Branchaud•4/15/24, 2:52 PM

Hello everyone! I'm currently migrating our app to Next-on-Pages and we are evaluating using KV instead of firebase. Quick question: I understand that KV bindings can be accessed in a runtime edge component (SSR/Workers). Can these same KV bindings be accessed in a server component (Static Rendering/Node.js) during the build process?

FelDev•4/16/24, 4:35 PM

About Next.js' 2MB cache limit

Failed to set fetch cache https://foobar.com/data Error: fetch for over 2MB of data can not be cached

There is a discussion in the Next.js repo about it https://github.com/vercel/next.js/discussions/48324
People talk about modifying the hardcoded 2MB limit in node_modules... which I'd rather not do.
Of course, some advise to keep fetch calls under 2MB... but that's not always possible.

One of our API calls returns almost 50MB of data.
I'm wondering how you guys deal with this?

FelDev•4/16/24, 4:36 PM

If we do increase the hardcoded 2MB limit, will CloudFlare be able to handle it?

neoney•4/17/24, 12:06 AM

changing my app from npm to bun, it's built on github actions... locally builds fine, on github it errors with

▲  Error: Importing "@vercel/next": require() of ES Module /home/runner/work/repo/repo/node_modules/string-width/index.js from /home/runner/work/repo/repo/node_modules/wide-align/align.js not supported.

▲  Error: Importing "@vercel/next": require() of ES Module /home/runner/work/repo/repo/node_modules/string-width/index.js from /home/runner/work/repo/repo/node_modules/wide-align/align.js not supported.

neoney•4/17/24, 12:07 AM

what the heck could that be?

neoney•4/17/24, 12:08 AM

Oh.

neoney•4/17/24, 12:08 AM

https://github.com/oven-sh/bun/issues/7539

GitHub

[package manager]: `string-width` is resolved incorrectly, causing ...

What version of Bun is running? 1.0.15+b3bdf22eb What platform is your computer? Darwin 23.1.0 arm64 arm What steps can reproduce the bug? see isaacs/jackspeak#5 (comment) run vite build What is th...

neoney•4/17/24, 12:08 AM

Bun bug

ANBU•4/17/24, 9:55 AM

Hey guys, any idea if CF_PAGES_URLCF_PAGES_URL is available in dev? If yes then any idea on how can I access it?

andrea_bhweb•4/17/24, 10:21 AM

Hi, I want to statically export most of the pages in my website, but still be able to use server actions, can it be achieved?

Aandrea_bhweb Hi, I want to statically export most of the pages in my website, but still be ab...

Hello, I’m Allie!•4/17/24, 10:25 AM

Not with next-on-pages atm

AANBU Hey guys, any idea if `CF_PAGES_URL` is available in dev? If yes then any idea o...

andrea_bhweb•4/17/24, 10:26 AM

From what I can see in the docs, and my own experience, those env variables only get defined during build; also note that the url in the CF_PAGES_URLCF_PAGES_URL var is the default .pages.dev.pages.dev one, if you plan on using a custom domain it's better to define your one env to specify it

AANBU Hey guys, any idea if `CF_PAGES_URL` is available in dev? If yes then any idea o...

Hello, I’m Allie!•4/17/24, 10:26 AM

I don't think so? Though you should be able to add it manually by putting it in a .dev.vars.dev.vars file:

CF_PAGES_URL=hello.pages.dev

CF_PAGES_URL=hello.pages.dev

HHello, I’m Allie!Not with <#1135899572141568050> atm

andrea_bhweb•4/17/24, 10:27 AM

ok, thanks; is it something that will be implemented at some point?

Aandrea_bhweb ok, thanks; is it something that will be implemented at some point?

Hello, I’m Allie!•4/17/24, 10:32 AM

Haven't heard anything about it. IIRC it is an issue from Next itself, not next-on-pages, as it expects to have control over routing, unless it is a fully static build

Lluna trying to use `@cloudflare/pages-plugin-vercel-og/api` and im getting a load of ...

Deo Kumar•4/17/24, 12:20 PM

It only works with workers not next-on-pages (if I'm not wrong). Either use @vercel/og or @cf-wasm/og

DDeo Kumar It only works with workers not next-on-pages (if I'm not wrong). Either use @ver...

luna•4/17/24, 12:21 PM

yeah i switched back to the vercel one.

Aandrea_bhweb From what I can see in the docs, and my own experience, those env variables only...

ANBU•4/17/24, 3:18 PM

Thanks for the info, I'll override this flag

neoney•4/17/24, 4:48 PM

Do durable object bindings work in next devnext dev?

Nneoney Do durable object bindings work in `next dev`?

Hello, I’m Allie!•4/17/24, 4:49 PM

They should? Can you share your

wrangler.toml

wrangler.toml

neoney•4/17/24, 4:49 PM

name = "sellhub-checkout"
compatibility_date = "2024-04-05"
compatibility_flags = ["nodejs_compat"]

[[services]]
binding = "WORKER"
service = "sellhub-checkout-cron"

# Bind a Durable Object. Durable objects are a scale-to-zero compute primitive based on the actor model.
# Durable Objects can live for as long as needed. Use these when you need a long-running "server", such as in realtime apps.
# Docs: https://developers.cloudflare.com/workers/runtime-apis/durable-objects
[[durable_objects.bindings]]
name = "LOCK"
class_name = "Lock"
script_name = 'sellhub-checkout-cron'

name = "sellhub-checkout"
compatibility_date = "2024-04-05"
compatibility_flags = ["nodejs_compat"]

[[services]]
binding = "WORKER"
service = "sellhub-checkout-cron"

# Bind a Durable Object. Durable objects are a scale-to-zero compute primitive based on the actor model.
# Durable Objects can live for as long as needed. Use these when you need a long-running "server", such as in realtime apps.
# Docs: https://developers.cloudflare.com/workers/runtime-apis/durable-objects
[[durable_objects.bindings]]
name = "LOCK"
class_name = "Lock"
script_name = 'sellhub-checkout-cron'

Nneoney ```toml name = "sellhub-checkout" compatibility_date = "2024-04-05" compatibilit...

Hello, I’m Allie!•4/17/24, 4:50 PM

That looks fine? If you try logging the envenv, do you see anything, or is it undefined?

neoney•4/17/24, 4:51 PM

well env.LOCK.idFromName and env.LOCK.get and the stub's fetch work

neoney•4/17/24, 4:51 PM

it just returns a 503 code

neoney•4/17/24, 4:51 PM

let me actually log the response text

neoney•4/17/24, 4:51 PM

[wrangler] Couldn't find

wrangler dev

wrangler dev

session for class "Lock" to proxy to

neoney•4/17/24, 4:51 PM

I do have wrangler dev running for the worker tho

neoney•4/17/24, 4:52 PM

Does the worker's wrangler.toml need something specified too?

Nneoney Does the worker's wrangler.toml need something specified too?

Hello, I’m Allie!•4/17/24, 4:52 PM

You have the DO bindings and the migrations defined?

neoney•4/17/24, 4:52 PM

Uhhh

neoney•4/17/24, 4:52 PM

I dont have anything

Nneoney I dont have anything

Hello, I’m Allie!•4/17/24, 4:53 PM

Yeah, you need to tell it what DOs it exposes

neoney•4/17/24, 4:53 PM

is it just

neoney•4/17/24, 4:53 PM

[[durable_objects.bindings]]
name = "LOCK"
class_name = "Lock"

[[durable_objects.bindings]]
name = "LOCK"
class_name = "Lock"

neoney•4/17/24, 4:53 PM

in the worker

Nneoney is it just

Hello, I’m Allie!•4/17/24, 4:53 PM

Yup, plus a migration that defines a "new_class"

Hello, I’m Allie!•4/17/24, 4:54 PM

https://developers.cloudflare.com/workers/wrangler/configuration/#migrations

Cloudflare Docs

Configuration - Wrangler · Cloudflare Workers docs

Use a

wrangler.toml

wrangler.toml

configuration file to customize the development and deployment setup for your Worker project and other Developer Platform …

neoney•4/17/24, 4:54 PM

lets see now

neoney•4/17/24, 4:54 PM

added these

neoney•4/17/24, 4:54 PM

same error let me try restarting page dev

neoney•4/17/24, 4:55 PM

SyntaxError: "undefined" is not valid JSON
at async Object.fetch (file:///home/neoney/code/sellhub/sellhub-checkout/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)

hey all, anyone have any experience with using durable objects from within next routes, locally? it

Similar Threads

Similar Threads

Similar Threads