Sir, which version of SvelteKit you are using? It may be related to my investigation.

RRastislav₡ore Sir, which version of SvelteKit you are using? It may be related to my investiga...

E

eftichis.•12/13/24, 12:05 PM

thank you for checking!

E

eftichis.•12/13/24, 12:06 PM

@sveltejs/kit 2.11.1

@sveltejs/kit 2.11.1

E

eftichis.•12/13/24, 12:06 PM

and

 svelte 5.12.0

 svelte 5.12.0

R

Rastislav₡oreOP•12/13/24, 12:08 PM

Right, my environment is based on the similar framework version. I am investigating and will keep you posted here. No solution is in the hands right away.

E

eftichis.•12/13/24, 12:08 PM

thank you so much - if required i can give you access to the repo

R

Rastislav₡oreOP•12/13/24, 12:09 PM

If repo is Open-source I will be happy to help you. It can help so many other people here as well.

to help

E

eftichis.•12/13/24, 12:09 PM

it's not open source though

R

Rastislav₡oreOP•12/13/24, 12:10 PM

Then just relevant parts are fine. I cannot sign any NDA, unfortunately…

R

Rastislav₡oreOP•12/13/24, 12:10 PM

Let me test my demo project seems same issue

E

eftichis.•12/13/24, 12:11 PM

haha that fine, i'm ok sharing it with you directly - it's just not for everyone here

K

kingmesal•12/13/24, 4:29 PM

is there a Type or a doc somewhere that has the full definition of the new and amazing sounding

wrangler.json

wrangler.json

?

I want to make use of this, because I have been needing JSON desperately.

Kkingmesal is there a Type or a doc somewhere that has the full definition of the new and a...

H

Hello, I’m Allie!•12/13/24, 4:58 PM

You can do

{
    "$schema": "node_modules/wrangler/config-schema.json"
}

{
    "$schema": "node_modules/wrangler/config-schema.json"
}

{
    "$schema": "node_modules/wrangler/config-schema.json"
}

{
    "$schema": "node_modules/wrangler/config-schema.json"
}

H

Hello, I’m Allie!•12/13/24, 4:58 PM

But it follows the exact same format as wrangler.toml, just with JSON instead of TOML

HHello, I’m Allie!You can do ```json { "$schema": "node_modules/wrangler/config-schema.json" }...

K

kingmesal•12/13/24, 5:04 PM

That is kind of a BIG but... because I can write the TOML 2 ways for many of the different parts of it, which easily obscures how to structure the json, depending on how your wrote the TOML. Would be great if there was a prebuild Typescript Type for that though.

Original message was deleted

K

kingmesal•12/13/24, 6:14 PM

We'll we dynamically / programmatically generate the Wrangler config, so having a typescript type here would be great.

I've just tried 4 different tools with that json to generate a type and they all error and in different ways...

Original message was deleted

K

kingmesal•12/13/24, 6:27 PM

Sorry, I mean, I'm using that config-schema.json to try to produce a Typescript type ... and they are not working.

Original message was deleted

K

kingmesal•12/13/24, 6:42 PM

thanks! that was exactly what I needed!!

WWalshy Ok I see what's going on, will need to contact another team

E

eftichis.•12/13/24, 7:25 PM

Hi Walshy, just wanted to follow up on this as i am still having the same bug without being able to get a proper error message to fix it

T

theo•12/13/24, 9:42 PM

would love to see wrangler config move to JS/TS. Would provide better intellisense, and make a lot of things much simpler!
see my comment here - https://github.com/cloudflare/workers-sdk/discussions/1951#discussioncomment-11403667

Ttheo would love to see wrangler config move to JS/TS. Would provide better intellisen...

K

kingmesal•12/14/24, 2:39 AM

Just ran my first test with it and it works great... And the type reference that Skye shared helped ensure as I was typing things in vs code showed me all the options :w00t:

T

theo•12/14/24, 2:53 AM

Nice that there is a type! But would love if it was just a wrangler.ts file that get automatically parsed

T

theo•12/14/24, 2:56 AM

Would make it much easier to start introducing things like hooks, or let you mess with the esbuild config, to do things like add plugins

K

karenr•12/16/24, 9:31 AM

Hi,

I am new to the cloudflare d1. I am confused as to why the local data persist when deploying to production? I don't want the local data used for testing to be part of the production build. Only when deleting the local data inside the .wrangler/state/v3/d1/* files it displays the production data during deployment.

right now, I have 21 records in the d1 dashboard and locally I have 5 records. But on production the 5 records are displaying instead of the 21 records. Am I missing something? Or is this how the cloudflare build works?

I am using opennext to deploy next.js in cloudflare. these are the default script during the opennext cloudflare set up

"scripts": {
"dev": "next dev",
"build": "next build",
"start": "next start",
"lint": "next lint",
"deploy": "cloudflare && wrangler deploy",
"preview": "cloudflare && wrangler dev",
"cf-typegen": "wrangler types --env-interface CloudflareEnv env.d.ts",
"build:worker": "cloudflare",
"dev:worker": "wrangler dev",
"preview:worker": "cloudflare && wrangler dev",
"deploy:worker": "npm run build:worker && wrangler deploy",
},

Appreciate any enlightenment. Also if this was previously asked and resolved, please kindly share the links to the post. Thank you!

G

Gad Mugambi•12/17/24, 5:36 AM

Cloudflare with nextjs kind of sucks.
Some of us have pre-existing enterprise nextjs app but can't try out cloudflare due to the 3mb worker limit.
Of course we will be willing to pay if we verify that cloudflare actually works.
Most tutorials just show starter apps, which are not actually true applications for production

GGad Mugambi Cloudflare with nextjs kind of sucks. Some of us have pre-existing enterprise n...

A

Abdul•12/17/24, 10:40 AM

What do you mean by 3mb worker limit? I don't see any limit.

Whilst i am building a production Nextjs app cloudflare pages and cloudflare workers... works Tremendous

AAbdul What do you mean by 3mb worker limit? I don't see any limit. Whilst i am buildi...

C

Chaika•12/17/24, 3:18 PM

Workers/Functions can be 3 MB max bundled (this is just the code, not including static assets) on free, or 10 MB on paid. This isn't the right channel for nextjs stuff anyway tho #next-on-pages

A

Alex•12/17/24, 4:44 PM

Hi. I am trying to have a simple proxy in functions/[[catchall]].js which will intercept few endpoints and proxy to a different url under the hood. However I keep running into weird error like this:

[wrangler:err] Error: internal error
    at async jsonError (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:10)
    at async drainBody (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-ensure-req-body-drained.ts:5:10)

[wrangler:err] Error: internal error
    at async jsonError (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:10)
    at async drainBody (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-ensure-req-body-drained.ts:5:10)

[wrangler:err] Error: internal error
    at async jsonError (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:10)
    at async drainBody (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-ensure-req-body-drained.ts:5:10)

[wrangler:err] Error: internal error
    at async jsonError (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-miniflare3-json-error.ts:22:10)
    at async drainBody (file:///D:/Frontend/node_modules/wrangler/templates/middleware/middleware-ensure-req-body-drained.ts:5:10)

my proxy is:

export default {
  async fetch(request, env, ctx) {
    console.log('proxy intercept', request, env);
    const url = new URL(request.url);
      const host = env.VITE_BACKEND_HOST;
      if (url.pathname.startsWith("/api")) {
        // handle api
        const pathname = url.pathname;
        const search = url.search;
        const pathWithParams = pathname + search;
        const newUrl = `${host}${pathWithParams}`;
        const cookies = parseAuthCookies(request.headers.get("cookie"), tabId);
        const newRequest = new Request(request);
        const token = cookies["Api.Token"];
        if (token != null) {
          newRequest.headers.set("Authorization", "Bearer " + token);
        }
        const response = await fetch(newUrl, newRequest); // exception
        console.log("proxy response", response);
        return response;
      }

    return fetch(url, request);
  }
}

export default {
  async fetch(request, env, ctx) {
    console.log('proxy intercept', request, env);
    const url = new URL(request.url);
      const host = env.VITE_BACKEND_HOST;
      if (url.pathname.startsWith("/api")) {
        // handle api
        const pathname = url.pathname;
        const search = url.search;
        const pathWithParams = pathname + search;
        const newUrl = `${host}${pathWithParams}`;
        const cookies = parseAuthCookies(request.headers.get("cookie"), tabId);
        const newRequest = new Request(request);
        const token = cookies["Api.Token"];
        if (token != null) {
          newRequest.headers.set("Authorization", "Bearer " + token);
        }
        const response = await fetch(newUrl, newRequest); // exception
        console.log("proxy response", response);
        return response;
      }

    return fetch(url, request);
  }
}

export default {
  async fetch(request, env, ctx) {
    console.log('proxy intercept', request, env);
    const url = new URL(request.url);
      const host = env.VITE_BACKEND_HOST;
      if (url.pathname.startsWith("/api")) {
        // handle api
        const pathname = url.pathname;
        const search = url.search;
        const pathWithParams = pathname + search;
        const newUrl = `${host}${pathWithParams}`;
        const cookies = parseAuthCookies(request.headers.get("cookie"), tabId);
        const newRequest = new Request(request);
        const token = cookies["Api.Token"];
        if (token != null) {
          newRequest.headers.set("Authorization", "Bearer " + token);
        }
        const response = await fetch(newUrl, newRequest); // exception
        console.log("proxy response", response);
        return response;
      }

    return fetch(url, request);
  }
}

export default {
  async fetch(request, env, ctx) {
    console.log('proxy intercept', request, env);
    const url = new URL(request.url);
      const host = env.VITE_BACKEND_HOST;
      if (url.pathname.startsWith("/api")) {
        // handle api
        const pathname = url.pathname;
        const search = url.search;
        const pathWithParams = pathname + search;
        const newUrl = `${host}${pathWithParams}`;
        const cookies = parseAuthCookies(request.headers.get("cookie"), tabId);
        const newRequest = new Request(request);
        const token = cookies["Api.Token"];
        if (token != null) {
          newRequest.headers.set("Authorization", "Bearer " + token);
        }
        const response = await fetch(newUrl, newRequest); // exception
        console.log("proxy response", response);
        return response;
      }

    return fetch(url, request);
  }
}

It never gets to response part. Always throws exception. When I test url like

https://localhost:5001/api/files/vault/bf09a8c8-54b3-4fb9-9d32-3a5e9d837ecb.jpeg

https://localhost:5001/api/files/vault/bf09a8c8-54b3-4fb9-9d32-3a5e9d837ecb.jpeg

in postman with auth header it works correctly. But when I do 8787 one in browser it doesn't And I see correct headers just before the call to inner fetch. Do you see if I am doing something wrong? Thank you.

NNH 🇮🇹Hey guys, I’m new to Cloudflare and Wrangler, so I apologize in advance if I hav...

E

Erik•12/17/24, 11:44 PM

i added node version to wrangler.toml

[vars]
NODE_VERSION = "18.18.0"

[vars]
NODE_VERSION = "18.18.0"

EErik i added node version to wrangler.toml ``` [vars] NODE_VERSION = "18.18.0" ```

N

NH 🇮🇹•12/18/24, 3:12 PM

Hey Erik,
thanks for your implementation

N

NH 🇮🇹•12/18/24, 3:12 PM

Appreciate your work

K

kchro3•12/19/24, 10:08 PM

i'd like to be able to test prompts locally with vitest, and i was hoping that i could make a test that would load my API keys from my .dev.vars file. can this be done? it looks like process.env is empty

Ttheo Would make it much easier to start introducing things like hooks, or let you mes...

K

kingmesal•12/20/24, 2:26 PM

If you happen to us VS Code, I just discovered this, and I started using it...
Add this to your project

.vscode/settings.json

.vscode/settings.json

  "json.schemas": [
    {
      "fileMatch": ["wrangler.json"],
      "url": "./node_modules/wrangler/config-schema.json"
    }
  ],

  "json.schemas": [
    {
      "fileMatch": ["wrangler.json"],
      "url": "./node_modules/wrangler/config-schema.json"
    }
  ],

  "json.schemas": [
    {
      "fileMatch": ["wrangler.json"],
      "url": "./node_modules/wrangler/config-schema.json"
    }
  ],

  "json.schemas": [
    {
      "fileMatch": ["wrangler.json"],
      "url": "./node_modules/wrangler/config-schema.json"
    }
  ],

Works perfectly! (acknowledging it is NOT exactly what you were asking for)

Kkingmesal If you happen to us VS Code, I just discovered this, and I started using it... A...

T

theo•12/20/24, 5:29 PM

thanks - definitely useful! Although what I'm really after is the ability to programatically drive it, and mess with esbuild instance

B

Bonadio•12/21/24, 4:14 PM

Trying to run worker in DEV but accessing R2 from production.
npx wrangler dev --config ./wrangler_t1.toml (this runs local) I have a /test endpoint and it works

now if I add --remote I no longer can access the /test endpoit
npx wrangler dev --config ./wrangler_t1.toml --remote

If I go to localhost:8787/test I get
[wrangler:inf] GET / 404 Not Found (2ms)

K

Kavatch•12/23/24, 5:38 PM

Hey, I am trying to use wrangler on a mac and getting this error:

 ~/IdeaProjects/workers-ms-render  master !3 ?2                                                                                                                                                    18:36:50 
❯ npx wrangler dev

 ⛅️ wrangler 3.99.0
-------------------

Running custom build: cargo install -q worker-build && worker-build --release
╭──────────────────────────────────────────────────────────────────────────────────────────────────╮
│  [b] open a browser, [d] open devtools, [l] turn off local mode, [c] clear console, [x] to exit  │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
[INFO]: 🎯  Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found in sysroot: "/opt/homebrew/Cellar/rust/1.83.0"

Used rustc from the following path: "/opt/homebrew/bin/rustc"

✘ [ERROR] Running custom build `cargo install -q worker-build && worker-build --release` failed. There are likely more logs from your build command above.


🪵  Logs were written to "/Users/alex/Library/Preferences/.wrangler/logs/wrangler-2024-12-23_17-37-02_261.log"

 ~/IdeaProjects/workers-ms-render  master !3 ?2                                                                                                                                                    18:36:50 
❯ npx wrangler dev

 ⛅️ wrangler 3.99.0
-------------------

Running custom build: cargo install -q worker-build && worker-build --release
╭──────────────────────────────────────────────────────────────────────────────────────────────────╮
│  [b] open a browser, [d] open devtools, [l] turn off local mode, [c] clear console, [x] to exit  │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
[INFO]: 🎯  Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found in sysroot: "/opt/homebrew/Cellar/rust/1.83.0"

Used rustc from the following path: "/opt/homebrew/bin/rustc"

✘ [ERROR] Running custom build `cargo install -q worker-build && worker-build --release` failed. There are likely more logs from your build command above.


🪵  Logs were written to "/Users/alex/Library/Preferences/.wrangler/logs/wrangler-2024-12-23_17-37-02_261.log"

 ~/IdeaProjects/workers-ms-render  master !3 ?2                                                                                                                                                    18:36:50 
❯ npx wrangler dev

 ⛅️ wrangler 3.99.0
-------------------

Running custom build: cargo install -q worker-build && worker-build --release
╭──────────────────────────────────────────────────────────────────────────────────────────────────╮
│  [b] open a browser, [d] open devtools, [l] turn off local mode, [c] clear console, [x] to exit  │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
[INFO]: 🎯  Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found in sysroot: "/opt/homebrew/Cellar/rust/1.83.0"

Used rustc from the following path: "/opt/homebrew/bin/rustc"

✘ [ERROR] Running custom build `cargo install -q worker-build && worker-build --release` failed. There are likely more logs from your build command above.


🪵  Logs were written to "/Users/alex/Library/Preferences/.wrangler/logs/wrangler-2024-12-23_17-37-02_261.log"

 ~/IdeaProjects/workers-ms-render  master !3 ?2                                                                                                                                                    18:36:50 
❯ npx wrangler dev

 ⛅️ wrangler 3.99.0
-------------------

Running custom build: cargo install -q worker-build && worker-build --release
╭──────────────────────────────────────────────────────────────────────────────────────────────────╮
│  [b] open a browser, [d] open devtools, [l] turn off local mode, [c] clear console, [x] to exit  │
╰──────────────────────────────────────────────────────────────────────────────────────────────────╯
[INFO]: 🎯  Checking for the Wasm target...
Error: wasm32-unknown-unknown target not found in sysroot: "/opt/homebrew/Cellar/rust/1.83.0"

Used rustc from the following path: "/opt/homebrew/bin/rustc"

✘ [ERROR] Running custom build `cargo install -q worker-build && worker-build --release` failed. There are likely more logs from your build command above.


🪵  Logs were written to "/Users/alex/Library/Preferences/.wrangler/logs/wrangler-2024-12-23_17-37-02_261.log"

Does someone know how I can fix it?

I already installed wasm32 as a target in rust but this also didn't do the trick

D

dapperdandev•12/24/24, 8:03 PM

I see a few posts that recommend uninstalling rust from homebrew and reinstalling with rust up:

curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh

DDM8tyProgrammer Hi is there way to reload Wrangler for html changes ? I am using wrangler 3.9...

H

Hello, I’m Allie!•12/30/24, 9:05 AM

I just use svelte dev

H

Hello, I’m Allie!•12/30/24, 9:05 AM

It gets you most of the way there

DDM8tyProgrammer is svelte dev commad ? could you elaborate ? ✗ npx svelte dev npm E...

H

Hello, I’m Allie!•12/30/24, 4:00 PM

Might be vite dev?

H

Hello, I’m Allie!•12/30/24, 4:00 PM

Just whatever the normal command for dev is

M

mindfulplays•12/31/24, 5:55 AM

Hi!

wrangler login

wrangler login

wrangler login

wrangler login does not work with VPN tunnel (e.g. tailscale) - it's very slow and fragile (errors out) even in normal situation. How do I open a bug or something to please please fix this frustrating login flow? There used be a way to at least paste the login code (the docs have some

curl

curl

thing that's even more fragile because wrangler errors out before I could even curl the localhost url)

M

mindfulplays•12/31/24, 5:55 AM

I spent close to an hour trying to get wrangler login work instead of doing actual work

M

mindfulplays•12/31/24, 5:56 AM

it's trying to do some magic stuff that is not fully working - I would love to get to a really dumb simple solution instead of this phoning home via localhost with my browser

S

snoob•1/2/25, 10:44 PM

Just came back from holiday and made an update to a workflow and when deploying with wrangler im getting this error:

binding AI of type ai failed to generate: internal error; please try again later or contact
  support [code: 10021]

binding AI of type ai failed to generate: internal error; please try again later or contact
  support [code: 10021]

binding AI of type ai failed to generate: internal error; please try again later or contact
  support [code: 10021]

binding AI of type ai failed to generate: internal error; please try again later or contact
  support [code: 10021]

Havent seen it before, and i was deploying just fine before. I reran wrangler types and updated wrangler to the latest version, any ideas why this happens?

U

usf•1/2/25, 10:46 PM

i'm having the same issue too

U

usf•1/2/25, 10:46 PM

i reported in #workers-ai channel

Uusf i'm having the same issue too

S

snoob•1/2/25, 11:00 PM

oh thank god haha

Sir, which version of SvelteKit you are using? It may be related to my investigation.

Similar Threads

Similar Threads

Similar Threads