I tried adding beside --test-scheduled but I am getting warning [wrangler-UserWorker:wrn] Miniflar

Jjumpspace I tried adding beside --test-scheduled but I am getting warning [wrangler-User...

M

MattIPv4•11/10/24, 4:52 PM

The latest release fixed it for me based on the repro I'd given them. If you're still seeing issues on the latest release, create a minimal repro and file an issue

Original message was deleted

J

jumpspaceOP•11/10/24, 5:16 PM

no I am usign __scheduled

J

jumpspaceOP•11/11/24, 1:05 AM

i created a new repo with cron job template. when making a request to the scheduled job the request never ends and keep processing while not running the scheduled job as well.

J

jumpspaceOP•11/11/24, 11:58 AM

ok folks. I figured out the Solution.

I was creating a scheduled job in A honojs file. That means implementing a scheduled worker in a -

npm create hono@latest my-app

npm create hono@latest my-app

npm create hono@latest my-app

npm create hono@latest my-app repo
That was causing all sorts of issue.

Then I created a fresh repo with

npm create cloudflare@latest -- my-first-worker

npm create cloudflare@latest -- my-first-worker

npm create cloudflare@latest -- my-first-worker

npm create cloudflare@latest -- my-first-worker then installed honojs to it and now the scheduled worker is working

N

naourass•11/16/24, 1:55 AM

Hi all, any idea what could cause this #miniflare error when trying to run a big insert query on a local D1 db through

getPlatformProxy()

getPlatformProxy()

getPlatformProxy()

getPlatformProxy()?

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112
        Error.captureStackTrace(err, this)
              ^

TypeError: fetch failed
    at Object.fetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/index.js:112:15)
    at async fetch3 (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/http/fetch.ts:90:19)
    at async ProxyClientBridge.dispatchFetch (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/index.ts:1647:20)
    at async ProxyStubHandler.#parseAsyncResponse (/home/naourass/web_exp/phoenix-astro-next/node_modules/miniflare/src/plugins/core/proxy/client.ts:339:15)
    at async SQLiteD1Session.batch (/home/naourass/web_exp/phoenix-astro-next/node_modules/src/d1/session.ts:82:24) {
  cause: SocketError: other side closed
      at Socket.onSocketEnd (/home/naourass/web_exp/phoenix-astro-next/node_modules/undici/lib/client.js:1118:22)
      at Socket.emit (node:events:530:35)
      at Socket.emit (node:domain:489:12)
      at endReadableNT (node:internal/streams/readable:1698:12)
      at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
    code: 'UND_ERR_SOCKET',
    socket: {
      localAddress: '127.0.0.1',
      localPort: 39446,
      remoteAddress: undefined,
      remotePort: undefined,
      remoteFamily: undefined,
      timeout: undefined,
      bytesWritten: 1148,
      bytesRead: 3678304
    }
  }
}

Node.js v22.11.0

N

naourass•11/16/24, 2:06 AM

Here's the code, it works fine with small data, but throws the error above when the batch data is relatively big:

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

const cfPlatformProxy = await getPlatformProxy()
const db = drizzle(cfPlatformProxy.env.DB)
await db.batch([...insertQueries])

K

Kimitri•11/16/24, 9:26 AM

is safe expose ids from wrangler binds in an public repository? There's some way to pass this throw environments variables?

KKimitri is safe expose ids from wrangler binds in an public repository? There's some way...

C

Cyb3r-Jak3•11/16/24, 9:52 AM

Everything in the wrangler file is safe to expose. The only exception is stuff like API keys which you should be using secrets for.

CCyb3r-Jak3 Everything in the wrangler file is safe to expose. The only exception is stuff l...

K

Kimitri•11/16/24, 9:55 AM

Thank you, I had this question because I didn't know if someone can access my Cloudflare resources with bind ids exposed in a wrangle file in a public repository

O

oof2win2•11/17/24, 9:44 PM

is

experimental-json-config

experimental-json-config

experimental-json-config

experimental-json-config safe to use with wrangler? or are there some pitfalls that i should know about if i want to use a json config instead

O

oof2win2•11/17/24, 9:53 PM

that sounds very usable - thank you!

A

Adam•11/18/24, 7:12 PM

is there any way to decide per-binding whether to use local vs remote? I have a problem where I want to develop some changes to a durable object script bound to a worker, but that worker needs to be bound to a remote r2 bucket in order to work. So I want to the locally running worker to the local durable object instance, but keep the remote binding to r2..

K

kaelys.js•11/19/24, 6:20 AM

Is there any way to run analytics engine bindings locally via wrangler or otherwise?

Kkaelys.js Is there any way to run analytics engine bindings locally via wrangler or otherw...

H

Hello, I’m Allie!•11/19/24, 2:51 PM

Not at the moment. I know there was some talk about stubbing them out at some point, but I don’t think that has happened yet

K

Kirk Ouimet•11/19/24, 11:11 PM

Is it possible to run wrangler dev with HTTPS enabled? I have

HTTP Only

HTTP Only

HTTP Only

HTTP Only cookies that need to get sent and chrome will not do that unless HTTPS is on

KKirk Ouimet Is it possible to run wrangler dev with HTTPS enabled? I have `HTTP Only` cookie...

C

Cyb3r-Jak3•11/20/24, 1:18 AM

If you use

wrangler dev --local-protocol https

wrangler dev --local-protocol https

wrangler dev --local-protocol https

wrangler dev --local-protocol https. It should work

C

Cyb3r-Jak3•11/20/24, 1:19 AM

It well be a self signed cert. You can pass --https-key-path and --https-cert-path to use your own certificate and key

K

Kirk Ouimet•11/20/24, 1:53 AM

Awesome thank you!

J

James•11/20/24, 4:53 AM

Hey can I change for how long I authorize wrangler to access my account for?

It seems like I used to get a day or so when I authorized wrangler local dev to use tools like Workers AI calls. Now I need to re-auth every few minutes and it's pretty irritating.

JJames Hey can I change for how long I authorize wrangler to access my account for? It...

H

Hello, I’m Allie!•11/20/24, 5:02 AM

IIRC as long as it is used, it should work indefinitely, or at least I’ve never been automatically logged out by it before

J

James•11/20/24, 5:10 AM

i'll try manual login via wrangler instead of it forcing it mid-flow with an AI request

K

Kimitri•11/20/24, 11:45 AM

I'm trying to run "wrangler dev" in a docker container locally for development, but I can't connect with the application, just when I run pnpm run dev I can connect. There's some setup that I need to do to run it on a docker container? I looked in documentation and I didn't find any thing

KKimitri I'm trying to run "wrangler dev" in a docker container locally for development, ...

C

Cyb3r-Jak3•11/20/24, 1:12 PM

I’m guessing you need to add

--ip 0.0.0.0

--ip 0.0.0.0

--ip 0.0.0.0

--ip 0.0.0.0 in the docker container

CCyb3r-Jak3 I’m guessing you need to add `--ip 0.0.0.0` in the docker container

K

Kimitri•11/20/24, 6:24 PM

thank you so much, now it's working perfect

B

bulldogandfisk•11/20/24, 6:57 PM

Hiya, I have a couple of DO migrations definitions, but get an error when deploying that I don't understand:

// Currently...
[[migrations]]
tag = 'v1'
new_classes = ['StateObject']

[[migrations]]
tag = 'v1'
new_classes = ['SocketManager']

// Currently...
[[migrations]]
tag = 'v1'
new_classes = ['StateObject']

[[migrations]]
tag = 'v1'
new_classes = ['SocketManager']

// Currently...
[[migrations]]
tag = 'v1'
new_classes = ['StateObject']

[[migrations]]
tag = 'v1'
new_classes = ['SocketManager']

// Currently...
[[migrations]]
tag = 'v1'
new_classes = ['StateObject']

[[migrations]]
tag = 'v1'
new_classes = ['SocketManager']

After the creation of

SocketManager

SocketManager

SocketManager

SocketManager on first deploy, on subsequent deploys I get this error from wrangler:

  Cannot apply new-class migration to class 'SocketManager' that is already depended on by existing
  Durable Objects [code: 10074]

  Cannot apply new-class migration to class 'SocketManager' that is already depended on by existing
  Durable Objects [code: 10074]

  Cannot apply new-class migration to class 'SocketManager' that is already depended on by existing
  Durable Objects [code: 10074]

  Cannot apply new-class migration to class 'SocketManager' that is already depended on by existing
  Durable Objects [code: 10074]

This error never appears for StateObject.

I can comment out the SocketManager migration and everything works just fine, but I feel that I'm missing something. Any guidance?

K

Kimitri•11/21/24, 1:54 AM

I have a public repository with Hono app, that I need to run test with Vitest-pool-workers in CI, the wrangler.toml is in .gitignore, there some way to run this tests without wrangler file or using the wrangler-action?

KKimitri I have a public repository with Hono app, that I need to run test with Vitest-po...

C

Cyb3r-Jak3•11/21/24, 2:03 AM

Why is the wrangler.toml in your gitignore?

W

Walshy•11/21/24, 2:05 AM

Everything in wrangler.toml is safe to share, account id/db id/etc are all ok to be public

CCyb3r-Jak3 Why is the wrangler.toml in your gitignore?

K

Kimitri•11/21/24, 2:23 AM

I thought if some one get my resources id they can use it

WWalshy Everything in wrangler.toml is safe to share, account id/db id/etc are all ok to...

K

Kimitri•11/21/24, 2:25 AM

so even if someone get my resources id they can't use it and I'll not charged for it?

J

James•11/21/24, 2:26 AM

Yes - they can’t use your resources without your account credentials. It’s safe

W

Walshy•11/21/24, 2:26 AM

Nope. They're scoped to your account. They'd need access to your account

K

Kimitri•11/21/24, 2:28 AM

thank you so much for clarify it

K

Kimitri•11/21/24, 11:21 AM

there some auto approve flag to this command?
"wrangler d1 migrations apply legion-db --remote=true"

I'm trying to use this command to apply migrations with git actions, but I can't find some flag to avoid type Y when I run this command

M

MarcosZapa•11/21/24, 2:05 PM

hi guys, silly question from a newbie here, I am getting starting with wrangler and I learned how to init a worked so far. Now, I have an old worker in the account I would like to update it in my local IDE, when I ran 'wrangler download worker-name' i got the error that the argument 'download' is unknown, so here I am.. how do I copy a worker into my local workers folder, so I can update and deploy it using wrangler? Couldn't find in the cloudflare docs neither, thanks in advance!

MMarcosZapa hi guys, silly question from a newbie here, I am getting starting with wrangler ...

J

James•11/21/24, 2:13 PM

Try the

—from-dash

—from-dash

—from-dash

—from-dash option in

wrangler init

wrangler init

wrangler init

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

Cloudflare Docs

Commands | Cloudflare Workers docs

Create, develop, and deploy your Cloudflare Workers with Wrangler commands.

JJames Try the `—from-dash` option in `wrangler init`: https://developers.cloudflare.co...

M

MarcosZapa•11/21/24, 2:49 PM

ah yes! the --from-dash command! thanks again!!

Original message was deleted

A

Adam•11/21/24, 3:38 PM

in that case I wonder if there's a way to configure an S3 client to point to the local R2 storage somehow? My problem is basically that I have a service which writes files to an R2 bucket using a standard S3 client because it runs outside of cloudflare, but then I have a cloudflare worker that wants to read those files out of R2. I can't get this setup to run locally because the cloudflare worker can only read from its own local version of r2, and the local service can only write to an s3-compatible API

B

BumblebeeSquare•11/21/24, 3:57 PM

hi all, how do i make Cloudflare build my pages sveltekit with wrangler@latest ? it keeps building it with 3.76 not 3.88 , i have compatibility date set up to latest one which is 11 on cf dashboard

S

surgery18•11/21/24, 10:09 PM

Hey guys, I just upgraded wrangler to 3.89 and now whatever I do, I cannot get my SERVICE to connect to my other wrangler instances. And yes, my other wrangler instance is persisting the data to the same .wrangler/state as the first one so all data can flow locally correctly. It was working before but now.

Services:
- POST: add-post [not connected]

I only get [not connected] now. What can I do to make that service connect again?

Thanks!

S

surgery18•11/22/24, 3:02 AM

3.88 does not work either
3.87 works.

So something from 3.88 broke the connection to Services.

V

Vladimir_dev•11/22/24, 5:52 AM

Hello. How to solve this error on windows 11?
wrangler 3.89.0

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

npx wrangler dev
✘ [ERROR] service core:user:hello-world: Uncaught LinkError: WebAssembly.Instance(): Import #9 "./index_bg.js" "__wbg_error_53abcd6a461f73d8": function import requires a callable

    at null.<anonymous> (shim.js:15:9)


                                                                                                                               
✘ [ERROR] The Workers runtime failed to start. There is likely additional logging output above.

Original message was deleted

V

Vladimir_dev•11/22/24, 2:53 PM

https://github.com/cloudflare/workers-rs/issues/668#issuecomment-2486930295

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

[patch.crates-io]
wasm-bindgen = { git = "https://github.com/rustwasm/wasm-bindgen" }

Original message was deleted

C

Cyb3r-Jak3•11/23/24, 4:22 PM

Typically means that you have the wrong output directory configured

Original message was deleted

C

Cyb3r-Jak3•11/23/24, 4:56 PM

What does the

Assets Uploaded

Assets Uploaded

Assets Uploaded

Assets Uploaded tab show on the deployment logs in Cloudflare?

Original message was deleted

C

Cyb3r-Jak3•11/23/24, 5:28 PM

Weird that all looks right to me. Maybe someone else will have an idea as to why it is not working

J

James•11/23/24, 6:17 PM

Can you share the URL and ideally a screenshot of the assets uploaded so we can check if there's any nesting?

N

NH 🇮🇹•11/23/24, 9:00 PM

Hey guys,
I’m new to Cloudflare and Wrangler, so I apologize in advance if I have misunderstood anything. I’m trying to deploy my Next.js website using Cloudflare Pages, so to build/deploy I'm using the

@cloudflare/next-on-pages@1

@cloudflare/next-on-pages@1

@cloudflare/next-on-pages@1

@cloudflare/next-on-pages@1 package. This requires me to add a

wrangler.toml

wrangler.toml

wrangler.toml

wrangler.toml file to my project root as it complained about a missing

nodejs_compat

nodejs_compat

nodejs_compat

nodejs_compat flag I needed to set, which I have done in the wrangler config.

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

name = "<PROJECT_NAME>"
compatibility_date = "2024-11-22"
compatibility_flags = ["nodejs_compat"]
pages_build_output_dir = ".vercel/output/static"

However, every time I try to deploy my site, I encounter the following issue:

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

21:46:32.059  Found wrangler.toml file. Reading build configuration...
21:46:32.064  pages_build_output_dir: .vercel/output/static
21:46:32.065  Build environment variables: (none found)
21:46:32.162  Successfully read wrangler.toml file.
21:46:32.300  Detected the following tools from environment: npm@9.6.7, nodejs@18.17.1
21:46:32.300  Installing project dependencies: npm clean-install --progress=false
21:46:33.815  npm WARN EBADENGINE Unsupported engine {
21:46:33.815  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.815  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.816  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:46:33.816  npm WARN EBADENGINE }
...
21:47:03.417  npm WARN EBADENGINE Unsupported engine {
21:46:33.417  npm WARN EBADENGINE   package: 'next@15.0.3',
21:46:33.417  npm WARN EBADENGINE   required: { node: '^18.18.0 || ^19.8.0 || >= 20.0.0' },
21:46:33.418  npm WARN EBADENGINE   current: { node: 'v18.17.1', npm: '9.6.7' }
21:47:04.782  You are using Node.js 18.17.1. For Next.js, Node.js version "^18.18.0 || ^19.8.0 || >= 20.0.0" is required.
21:47:04.798  Error: Command "npm run build" exited with 1

I tried adding beside --test-scheduled but I am getting warning [wrangler-UserWorker:wrn] Miniflar

Similar Threads

Similar Threads

Similar Threads