let's make a thread if you have issues

M

Matt•4/14/24, 2:29 AM

done haha sorry for the spam

M

Matt•4/14/24, 2:30 AM

so I think im a little confused... when I initially started this, I setup the example nextjs cf pages example and just created a DO, and added the binding in the wrangler.toml for the next app and tried to call the DO from inside a next route but that didnt work at all

M

Matt•4/14/24, 2:30 AM

youre saying that should?

M

Matt•4/14/24, 2:32 AM

alright cool, im going to spin up a DO in its own project and look to implement what you described =X

M

Matt•4/14/24, 2:32 AM

thanks for the help man

M

Matt•4/14/24, 2:37 AM

howd you realize you had to run a worker in addition to everything? im not sure if i just missed it or what, unfortunately in the basic demo for the next pages setup they leave off DO and just show KV which seems much easier

M

Matt•4/14/24, 2:41 AM

youre the first person to help on disc so thanks again haha, not sure if its quiet around here because of the weekend or what

M

Matt•4/14/24, 5:03 AM

sorry to bug you again @Alexandеr , I just got around to trying what you had said - so i have a new project for the DO thats just from the template cf provides, i run that with the command you provided point to the .wrangler state dir in my pages next app - and then my wrangler.toml in my next app has the bindings + script name pointed at the script for the DO in the DO project... i start next... and try hitting a route in the next app that tries to get an id/stub/fetch against the DO but stub/id are still undefined

M

Matt•4/14/24, 5:05 AM

i actually get

"[wrangler] Couldn't find `wrangler dev` session for class \"MyDurableObject\" to proxy to"

"[wrangler] Couldn't find `wrangler dev` session for class \"MyDurableObject\" to proxy to"

"[wrangler] Couldn't find `wrangler dev` session for class \"MyDurableObject\" to proxy to"

"[wrangler] Couldn't find `wrangler dev` session for class \"MyDurableObject\" to proxy to"

M

Matt•4/14/24, 5:10 AM

I just realized you were saying to use worker name for script_name and not file name right? i changed script_name= to the worker name from :6284/workers and now im getting:

"SyntaxError: \"undefined\" is not valid JSON\n    at async Object.fetch (file:///opt/homebrew/lib/node_modules/wrangler/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)

"SyntaxError: \"undefined\" is not valid JSON\n    at async Object.fetch (file:///opt/homebrew/lib/node_modules/wrangler/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)

"SyntaxError: \"undefined\" is not valid JSON\n    at async Object.fetch (file:///opt/homebrew/lib/node_modules/wrangler/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)

"SyntaxError: \"undefined\" is not valid JSON\n    at async Object.fetch (file:///opt/homebrew/lib/node_modules/wrangler/node_modules/miniflare/dist/src/workers/core/entry.worker.js:944:22)

M

Matt•4/14/24, 5:16 AM

my attempt to use the DO from a route looks like this:

import type { NextRequest } from "next/server";
import { getRequestContext } from "@cloudflare/next-on-pages";

export const runtime = "edge";

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

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

  console.log("env", context.env); // env has my DO in it
  console.log({ id, stub }); // id and stub are undefined

  // what should be here?
  // i tried passing "request" but it says it cant get a url from it so i just put a url that works for now
  const x = await stub.fetch("http://localhost/whatever");
  const text = await x.text();

  return Response.json({ text });
}

import type { NextRequest } from "next/server";
import { getRequestContext } from "@cloudflare/next-on-pages";

export const runtime = "edge";

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

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

  console.log("env", context.env); // env has my DO in it
  console.log({ id, stub }); // id and stub are undefined

  // what should be here?
  // i tried passing "request" but it says it cant get a url from it so i just put a url that works for now
  const x = await stub.fetch("http://localhost/whatever");
  const text = await x.text();

  return Response.json({ text });
}

import type { NextRequest } from "next/server";
import { getRequestContext } from "@cloudflare/next-on-pages";

export const runtime = "edge";

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

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

  console.log("env", context.env); // env has my DO in it
  console.log({ id, stub }); // id and stub are undefined

  // what should be here?
  // i tried passing "request" but it says it cant get a url from it so i just put a url that works for now
  const x = await stub.fetch("http://localhost/whatever");
  const text = await x.text();

  return Response.json({ text });
}

import type { NextRequest } from "next/server";
import { getRequestContext } from "@cloudflare/next-on-pages";

export const runtime = "edge";

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

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

  console.log("env", context.env); // env has my DO in it
  console.log({ id, stub }); // id and stub are undefined

  // what should be here?
  // i tried passing "request" but it says it cant get a url from it so i just put a url that works for now
  const x = await stub.fetch("http://localhost/whatever");
  const text = await x.text();

  return Response.json({ text });
}

M

Matt•4/14/24, 6:45 AM

i started debugging and the issue is

request.cf

request.cf

request.cf

request.cf

being undefined when the code tries to JSON.stringify it

M

Matt•4/14/24, 6:46 AM

https://github.com/cloudflare/workers-sdk/blame/main/packages/wrangler/src/dev/miniflare.ts#L124

GitHub

Blaming workers-sdk/packages/wrangler/src/dev/miniflare.ts at main ...

Home to Wrangler, the CLI for Cloudflare Workers® - Blaming workers-sdk/packages/wrangler/src/dev/miniflare.ts at main · cloudflare/workers-sdk

M

Matt•4/14/24, 6:48 AM

looks like the "bug"? was introduced last week

M

Matt•4/14/24, 6:49 AM

hah

M

Matt•4/14/24, 6:49 AM

M

Matt•4/14/24, 6:49 AM

line 124

M

Matt•4/14/24, 6:49 AM

M

Matt•4/14/24, 6:50 AM

looks like they handle it on 162

M

Matt•4/14/24, 6:50 AM

but not 124 potentially

Original message was deleted

M

Matt•4/14/24, 3:38 PM

3.34.2 works! i cant believe how long I spent trying to get this working yesterday and it was never going to lol

oof

M

Matt•4/14/24, 3:39 PM

whats the best course now? ping someone on disc or just open a github issue?

M

Matt•4/14/24, 3:40 PM

im not sure if the bug is request.cf being undefined to begin with but the quick fix is to just handle it before the JSON.stringify call i mentiond up above

M

Matt•4/14/24, 3:51 PM

haha sadly im east coast too

M

Matt•4/14/24, 3:52 PM

monday off from work up here in boston so i figured i could splurge a bit lol

let's make a thread if you have issues

Similar Threads