What is the `pages` npm package and why would you need it? That’s over a decade old and for AngularJ

JJames What is the `pages` npm package and why would you need it? That’s over a decade ...

A

awful•3/25/25, 2:38 AM

https://developers.cloudflare.com/workers/wrangler/commands/#pages

J

JamesOP•3/25/25, 2:38 AM

That’s a wrangler command - you don’t need to install

pages

pages

from npm.

npx wrangler pages dev

npx wrangler pages dev

for example will run a local dev server for Cloudflare Pages

A

awful•3/25/25, 2:39 AM

Thanks I probably forgot to type wrangler

A

adt•3/25/25, 12:51 PM

Hey All! Im trying to run an Astro SSR app with cloudflare. I'm having type conflicts with the wrangler generated types when calling client side web apis from a client side script... For example, calling fetch from a client side script will reference the workerd fetch type and not the web api. Is there a work around or am i missing something?

C

Cibulka•3/26/25, 5:36 PM

Why don't my static files load

C

Cibulka•3/26/25, 5:36 PM

all of them just give 404 errors

V

veeque•3/26/25, 5:59 PM

running

wrangler d1 execute --help

wrangler d1 execute --help

I see the option for

-y

-y

. Is there the opposite?

-n

-n

? I need to have the

.sql

.sql

file for D1 be created (to get its name) by running

wrangler d1 execute id-development -e development --command ' ' --local

wrangler d1 execute id-development -e development --command ' ' --local

which will result in an error and I don't think spamming Cloudflare with random stuff is something I should do

V

veeque•3/26/25, 6:10 PM

When the command fails it asks:

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

Would you like to report this error to Cloudflare? Wrangler's output and the error details will be shared with the Wrangler team to help us diagnose and fix the issue. (Y/n)

, and using

-y

-y

would say yes every time, also

| yes n

| yes n

is not an option

V

veeque•3/26/25, 6:49 PM

ohh that one's good, ty

D

dan•3/26/25, 8:04 PM

does anyone have any tips for working with

wrangler types

wrangler types

in monorepo packages? I have multiple workers that can bind to one another (as well as DOs) but I'm not sure how to get a typed reference to

workers/my-agent

workers/my-agent

from

apps/api

apps/api

without

apps/api

apps/api

importing from

workers

workers

(which I don't want)

D

dan•3/26/25, 8:05 PM

this is really annoying and common in my codebase right now, i'm in a monorepo package that shouldn't depend on a worker in the monorepo so i have no idea how to resolve these types

S

shay•3/26/25, 8:23 PM

how can i debug errors thrown by

wrangler dev

wrangler dev

like the one below? not sure if it's a vite issue (i'm migrating from remix's classic compiler) but the vite build itself completes successfully (

remix vite:build

remix vite:build

).

⎔ Starting local server...
✘ [ERROR] service core:user:discohook-site: Uncaught TypeError: d7t is not a function
    at null.<anonymous> (server.js:452:17894)

⎔ Starting local server...
✘ [ERROR] service core:user:discohook-site: Uncaught TypeError: d7t is not a function
    at null.<anonymous> (server.js:452:17894)

⎔ Starting local server...
✘ [ERROR] service core:user:discohook-site: Uncaught TypeError: d7t is not a function
    at null.<anonymous> (server.js:452:17894)

⎔ Starting local server...
✘ [ERROR] service core:user:discohook-site: Uncaught TypeError: d7t is not a function
    at null.<anonymous> (server.js:452:17894)

i'm just not sure where to begin. to my knowledge,

server.js

server.js

is not a file that has been generated by my build

A

April•3/27/25, 9:06 AM

vc

Ddan does anyone have any tips for working with `wrangler types` in monorepo packages...

D

DaniFoldi•3/27/25, 3:21 PM

yeah my recommendation is to not use workers types, or use it once and then fix it manually

D

DaniFoldi•3/27/25, 3:21 PM

unfortunately there are still many missing features for me to be able to recommend it

D

DaniFoldi•3/27/25, 3:22 PM

manually the way you would override it is to use

DurableObjectNamespace<import('where your DO class is exported').exportname>

DurableObjectNamespace<import('where your DO class is exported').exportname>

or

Service<same import

Service<same import

for service bindings

D

dan•3/27/25, 3:22 PM

right but that breaks dependency chains in some cases

D

dan•3/27/25, 3:22 PM

or results in cyclical depencies

D

dan•3/27/25, 3:23 PM

what i'm doing right now which kind of works is manually declaring the interfaces in a standalone package that has no dependencies that can be imported like:

declare global {
  namespace Dependencies {
    type RecipeParser = Service<RecipeParserWorker>;
    interface RecipeParserWorker extends WorkerEntrypoint<unknown> {
      /**
       * Main entry point that handles recipe parsing requests
       */
      fetch(request: Request): Promise<Response>;
      parseRecipeFromUrl(recipeUrl: string): Promise<Response>;
      modifyRecipe(input: { recipe: RecipeSchema; instructions: string }): Promise<Response>;
      /**
       * Parse recipe using a two-phase approach:
       * 1. Try fetch first (faster, less resource intensive)
       * 2. Fall back to puppeteer if fetch doesn't yield good results
       */
    }

    class RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

declare global {
  namespace Dependencies {
    type RecipeParser = Service<RecipeParserWorker>;
    interface RecipeParserWorker extends WorkerEntrypoint<unknown> {
      /**
       * Main entry point that handles recipe parsing requests
       */
      fetch(request: Request): Promise<Response>;
      parseRecipeFromUrl(recipeUrl: string): Promise<Response>;
      modifyRecipe(input: { recipe: RecipeSchema; instructions: string }): Promise<Response>;
      /**
       * Parse recipe using a two-phase approach:
       * 1. Try fetch first (faster, less resource intensive)
       * 2. Fall back to puppeteer if fetch doesn't yield good results
       */
    }

    class RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

declare global {
  namespace Dependencies {
    type RecipeParser = Service<RecipeParserWorker>;
    interface RecipeParserWorker extends WorkerEntrypoint<unknown> {
      /**
       * Main entry point that handles recipe parsing requests
       */
      fetch(request: Request): Promise<Response>;
      parseRecipeFromUrl(recipeUrl: string): Promise<Response>;
      modifyRecipe(input: { recipe: RecipeSchema; instructions: string }): Promise<Response>;
      /**
       * Parse recipe using a two-phase approach:
       * 1. Try fetch first (faster, less resource intensive)
       * 2. Fall back to puppeteer if fetch doesn't yield good results
       */
    }

    class RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

declare global {
  namespace Dependencies {
    type RecipeParser = Service<RecipeParserWorker>;
    interface RecipeParserWorker extends WorkerEntrypoint<unknown> {
      /**
       * Main entry point that handles recipe parsing requests
       */
      fetch(request: Request): Promise<Response>;
      parseRecipeFromUrl(recipeUrl: string): Promise<Response>;
      modifyRecipe(input: { recipe: RecipeSchema; instructions: string }): Promise<Response>;
      /**
       * Parse recipe using a two-phase approach:
       * 1. Try fetch first (faster, less resource intensive)
       * 2. Fall back to puppeteer if fetch doesn't yield good results
       */
    }

    class RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

D

dan•3/27/25, 3:23 PM

RecipeParser

RecipeParser

works fine, i'm struggling with DO declarations though, like that namespace doesn't actually work (it doesnt' give errors, but

test()

test()

doesn't appear on the type when consuming it

D

DaniFoldi•3/27/25, 3:23 PM

yeah you can do this, or you can pre-generate the type and publish that to a repository and import that

Ddan `RecipeParser` works fine, i'm struggling with DO declarations though, like that...

D

DaniFoldi•3/27/25, 3:24 PM

for that you need to use the import from cloudflare:workers

D

dan•3/27/25, 3:26 PM

which import? I am using DurableObject from there

D

dan•3/27/25, 3:26 PM

the tsconfig of this dependencies package has

"types": ["@cloudflare/workers-types"]

"types": ["@cloudflare/workers-types"]

D

dan•3/27/25, 3:33 PM

ah i just got it

D

dan•3/27/25, 3:33 PM

    type RecipeAgent = Rpc.DurableObjectBranded & {
      test: () => Promise<void>;
    };

    type RecipeAgent = Rpc.DurableObjectBranded & {
      test: () => Promise<void>;
    };

D

dan•3/27/25, 3:33 PM

this seems to work

D

dan•3/27/25, 3:38 PM

ah ok... there are mulitple DO exports

DDaniFoldi for that you need to use the import from cloudflare:workers

D

dan•3/27/25, 3:38 PM

i undertand this now

D

dan•3/27/25, 3:38 PM

import type { DurableObject } from 'cloudflare:workers';

declare global {
  namespace Dependencies {
    interface RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

import type { DurableObject } from 'cloudflare:workers';

declare global {
  namespace Dependencies {
    interface RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

import type { DurableObject } from 'cloudflare:workers';

declare global {
  namespace Dependencies {
    interface RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

import type { DurableObject } from 'cloudflare:workers';

declare global {
  namespace Dependencies {
    interface RecipeAgent extends DurableObject<unknown> {
      test: () => Promise<void>;
    }

    type RecipeAgentNamespace = DurableObjectNamespace<RecipeAgent>;
  }
}

works

D

dan•3/27/25, 3:38 PM

was a conflict with the one from worker types

D

DaniFoldi•3/27/25, 3:40 PM

yeah the default one doesn't have RPC types, for backwards compatibility reasons

D

DaniFoldi•3/27/25, 3:41 PM

and you need the entrypoint to be there at runtime becase RPC reasons

D

DaniFoldi•3/27/25, 3:41 PM

so the tsconfig types entry isn't enough for that

D

dan•3/27/25, 3:43 PM

copy, wasn't aware there was a distinction

D

dan•3/27/25, 3:43 PM

i think this is the best thing to do now, and maybe write a bash script to replace instances of these bindings with the types from my dependencies package after running

wrangler types

wrangler types

D

dan•3/27/25, 3:44 PM

instance methods on service bindings or DOs don't really change frequently so it's not a big deal

D

dan•3/27/25, 3:44 PM

but this is definitely a really awkward aspect of developing with workers

Ddan but this is definitely a really awkward aspect of developing with workers

D

DaniFoldi•3/27/25, 5:30 PM

Agreed

J

JacobMGEvans•3/28/25, 2:12 AM

I am about to get REAL into Durable Objects, be pepared for an onslaught of stupid questions

V

Vlady•3/29/25, 1:10 AM

Y'all, my build used to work with wrangler 3, but not with v4. Why is wrangler expecting the config to be in the build folder when I build my app and run

wrangler dev

wrangler dev

?

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

There is a deploy configuration at ".wrangler/deploy/config.json".

  But the redirected configuration path it points to, "build/server/wrangler.json", does not exist.

wrangler.toml

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

compatibility_date = "2025-02-10"
compatibility_flags = ["nodejs_compat"]
assets = { directory = "./build/client" }
main = './src/entry.worker.ts'

I'm running my

yarn preview

yarn preview

yarn preview

yarn preview script, here's how it's defined in package.json

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

 "preview": "yarn build && wrangler dev",
 "build": "react-router build",

What am I doing wrong here? I want to test if my React Router 7 build works locally.

V

Vlady•3/29/25, 1:14 AM

I'm following the official template and the error is the same if I match the config and commands 1 to 1 https://github.com/cloudflare/templates/blob/staging/react-router-starter-template/wrangler.json

V

Vlady•3/29/25, 1:19 AM

I deleted this and it started working, not sure what generated it in the first place

T

thomasgauvin•3/30/25, 2:20 AM

How do you run a Worker project, within another Worker project? Wrangler seems to hang on detecting multiple wrangler.jsonc files, need to manually indicate which to use but it doesn't seem to be a parameter? https://developers.cloudflare.com/workers/wrangler/commands/#dev

Tthomasgauvin How do you run a Worker project, within another Worker project? Wrangler seems t...

M

MattIPv4•3/30/25, 3:49 AM

Try the

--config

--config

--config

--config flag? It’s documented in other places as doing what you want here

T

thomasgauvin•3/30/25, 3:51 AM

Yep, that ended up working, thanks @MattIPv4

M

MattIPv4•3/30/25, 3:51 AM

And file an issue for updating the err to include that

T

thomasgauvin•3/30/25, 3:52 AM

Yeah, need to explain what's wrong + how to fix it in the error log, otherwise it's spam in the channel (like me rn)

M

MattIPv4•3/30/25, 3:52 AM

And if you want, an issue for the docs to make it clearer that’s a global flag :nod:

A

Alejandro Mery•3/31/25, 7:11 PM

hi, when trying to deploy from a dev container, I get a link for oauth but when approving it I'm told "No redirect uri set!" and later wrangler fails with "timed out waiting for authorization code"

any idea how to get this to work again?

What is the `pages` npm package and why would you need it? That’s over a decade old and for AngularJ

Similar Threads

Similar Threads

Similar Threads