Cloudflare with nextjs kind of sucks. Some of us have pre-existing enterprise nextjs app but can't

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

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"

[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

.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

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

S

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

yeah im like trying everything to figure out whats happening

M

Mitya•1/3/25, 10:12 AM

Out of nowhere I'm suddenly today getting this when I run

npm run dev

npm run dev

npm run dev

npm run dev

I've updated Wrangler to the latest version but no change. Anyone know what's behind this?

M

Mitya•1/3/25, 10:12 AM

The error is coming from within Wrangler, not my app, seemingly

M

Mitya•1/3/25, 11:49 AM

Restarting my system fixed it, though I'm not sure why

L

Lemon•1/4/25, 12:34 AM

Hey guys I'm tryna build and publish my pages in my monorepo (turborepo)
I have the following

workflow.yml

workflow.yml

workflow.yml

workflow.yml and properly setup the secrets as attached but I get the error that the env variables are missing.
Did anyone encountered something like this in a monorepo?

I console logged the value of the variables and its there but the CLI doesnt pick them up

for the build it runs

npm run build

npm run build

npm run build

npm run build that runs build commands (like

astro build

astro build

astro build

astro build or

wrangler build

wrangler build

wrangler build

wrangler build for my workers with Hono) then

wrangler pages deploy ./dist

wrangler pages deploy ./dist

wrangler pages deploy ./dist

wrangler pages deploy ./dist or

wrangler deploy

wrangler deploy

wrangler deploy

wrangler deploy for my workers...etc.

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

name: ⚡ Deploy to Cloudflare

on:
  push:
    branches:
      - master

jobs:
  deploy:
    runs-on: ubuntu-latest
    name: ☁️ Deploy
    steps:
      - name: 📥 Checkout
        uses: actions/checkout@v3

      - name: ⚙️ Use Node.js 18.x
        uses: actions/setup-node@v1
        with:
          node-version: 18.x

      - name: ⬇️ Install dependencies
        run: npm install

      - name: 🔨 Build apps & packages
        run: npm run build

      - name: 🚀 Deploy apps
        run: npm run deploy
        env:
          CLOUDFLARE_ACCOUNT_ID: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}
          CLOUDFLARE_API_TOKEN: ${{ secrets.CLOUDFLARE_API_TOKEN }}
          CLOUDFLARE_EMAIL: ${{ secrets.CLOUDFLARE_EMAIL }}

Original message was deleted

L

Lemon•1/6/25, 4:40 AM

Nah I pass
The action doesn’t support multiple folders afaik especially when running different commands ex for pages and workers there are two separate commands

I deploy 6 sites and the action is limited to 5 based on the docs
All I want is to make the stupid CLI work because it ain’t reading the env variable that is clearly present
It worked with a year ago but now that repo is broken too someone changed something…

Z

zecanard•1/6/25, 7:21 AM

Does anyone know how to upload metadata with

wrangler kv bulk put

wrangler kv bulk put

wrangler kv bulk put

wrangler kv bulk put? I tried following the docs, passing the following JSON:

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

[
    {
        "key": "key1",
        "value": "value1",
        "metadata": "{ \"metadata1\": 1 }"
    },
    {
        "key": "key2",
        "value": "value2",
        "metadata": "{ \"metadata2\": 2 }"
    }
]

But I get the following error:

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

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

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

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

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

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

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

✘ [ERROR] Unexpected JSON input from "kv.json".

  Each item in the array should be an object that matches:
  
  interface KeyValue {
    key: string;
    value: string;
    expiration?: number;
    expiration_ttl?: number;
    metadata?: object;
    base64?: boolean;
  }
  
  The item at index 0 is {"key":"key1","value":"value1","metadata":"{ \"metadata1\": 1 }"}
  The item at index 1 is {"key":"key2","value":"value2","metadata":"{ \"metadata2\": 2 }"}

What kind of

object

object

object

object do we need to pass for the

metadata

metadata

metadata

metadata? In contrast,

wrangler kv key put --metadata

wrangler kv key put --metadata

wrangler kv key put --metadata

wrangler kv key put --metadata does accept a JSON-serialized string and works as expected.

The

bulk put

bulk put

bulk put

bulk put works as expected if I just pass the

key

key

key

key and

value

value

value

value, or with the example provided in the docs (passing an

expiration_ttl

expiration_ttl

expiration_ttl

expiration_ttl).

J

James•1/6/25, 4:34 PM

wrangler adjacent with workers-types, but just want to make sure folks are aware of https://github.com/cloudflare/workerd/pull/3278. There's a whole bunch of proposed breaking changes there that need some more careful thought/consideration imo.

J

James•1/6/25, 4:53 PM

Thanks! There's countless examples of people using the types like

AiTextGenerationInput

AiTextGenerationInput

AiTextGenerationInput

AiTextGenerationInput, etc. so I'm looking forward to see the direction here. My 2c: it either needs to be a new major workers-types, or walked back so to be an extension of types instead of introducing breaking changes.

J

James•1/6/25, 4:54 PM

I'm not personally convinced a separate package makes sense, given how it bypasses all of the great OSS process in workers-types, not to mention is a

0.x.x

0.x.x

0.x.x

0.x.x version so RIP semver, which for a GA product is not great.

J

James•1/6/25, 4:54 PM

But thanks for the insight!

T

Torianna•1/6/25, 5:02 PM

in most codebases, using

any

any

is forbidden

T

Torianna•1/6/25, 5:04 PM

like, the whole point of types is to be typed, not bypassed with

any

any

J

Jürgen Leschner•1/6/25, 5:21 PM

Hi - I was wondering if there is anything you can share about vite environments and wrangler.
It would be really cool if vite-based dev frameworks could be nicely integrated with "regular" cloudflare workers for local dev workflows.

J

Jürgen Leschner•1/6/25, 5:32 PM

Related question (adjacent to wrangler) I was wondering if Cloudflare will also help to extend some of the other framework adapters e.g. @astro/cloudflare, to enable them to use features like Durable Objects. (Cloudflare adapter is unable to export D...)

J

Jürgen Leschner•1/6/25, 5:45 PM

connecting those 2 questions - i guess what I'm hoping is that adapters might get simpler if the new vite integration allowed for co-development of workers/DOs for server-side apis together with the front-end framework components that depend on those services.

Ppenalosa It's something we're actively working on! cc @James Opstad —what's the best plac...

L

Likeawinnaar•1/6/25, 5:46 PM

Pls loom to my ticket

L

Likeawinnaar•1/6/25, 5:46 PM

general-helpHelp needed

L

Likeawinnaar•1/6/25, 5:47 PM

Look*

Cloudflare with nextjs kind of sucks. Some of us have pre-existing enterprise nextjs app but can't

Similar Threads

Similar Threads

Similar Threads