No, I mean that as a part of the build process for `wrangler`, Actions can pull the Zod schema, and

H

So you get JSON Schema for your editor to validate your config, and Zod for

wrangler

wrangler

to validate it

HHello, I’m Allie!No, I mean that as a part of the build process for `wrangler`, Actions can pull ...

A

amorfati•6/22/23, 7:04 PM

that would be nice. Although I don't know if Zod can have a

description

description

description

description field like a JSON schema

HHello, I’m Allie!https://www.npmjs.com/package/zod-to-json-schema

A

amorfati•6/22/23, 7:04 PM

https://www.npmjs.com/package/json-schema-to-zod

npm

json-schema-to-zod

Converts JSON schema objects or files into Zod schemas. Latest version: 0.6.3, last published: 4 months ago. Start using json-schema-to-zod in your project by running

npm i json-schema-to-zod

npm i json-schema-to-zod

npm i json-schema-to-zod

npm i json-schema-to-zod. There are 13 other projects in the npm registry using json-schema-to-zod.

Aamorfati that would be nice. Although I don't know if Zod can have a `description` field ...

A

amorfati•6/22/23, 7:06 PM

Actually does!

.describe()

.describe()

.describe()

.describe(). nice

A

amorfati•6/22/23, 7:07 PM

anyway we can help with the zod schema if it's public right now? Would gladly contribute

WWalshy Off topic but is there a vod for your turborepo stream?

J

JacobMGEvans•6/22/23, 7:19 PM

As of now it is on https://twitch.tv/jacobmgevans/videos eventually I will be a edited version on YT

Twitch

JacobMGEvans Videos - Twitch

Watch all of JacobMGEvans's best archives, VODs, and highlights on Twitch. Find their latest Just Chatting streams and much more right here.

V

Valerii M•6/23/23, 12:26 PM

Hello, colleagues!
Could you please take a small glance on this issue which I just opened?
https://github.com/cloudflare/workers-sdk/issues/3515

Is it some known problem and there's any workaround for that?

UPD: It's already resolved in Github issue

GitHub

🐛 BUG: `wrangler dev` doesn't work with KV on Node.JS >= 18 · Issue...

Which Cloudflare product(s) does this pertain to? KV What version of Wrangler are you using? 3.1.1 What operating system are you using? MacOS (13.2.1 (22D68)), Ubuntu 22.04.2 LTS Describe the Bug L...

B

Bink•6/24/23, 6:54 AM

15:31:14.399 ✘ [ERROR] Error: Pages only supports files up to 26.2 MB in size
15:31:14.399
15:31:14.399 cache/webpack/client-production/0.pack is 165 MB in size
15:31:14.399
15:31:14.400
15:31:14.400 If you think this is a bug then please create an issue at https://github.com/cloudflare/workers-sdk/issues/new/choose
15:31:14.412 Failed: upload process exited with code: 1
15:31:15.350 Failed: an internal error occurred
15:31:15.350 Error: Failed to publish assets. For support, join our Discord (https://discord.gg/cloudflaredev) or create a ticket and reference the deployment ID: 07b4492a-a308-4312-9398-5cb467884de2

GitHub

Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.

B

Bink•6/24/23, 6:55 AM

please help all mates

BBink 15:31:14.399 ✘ [ERROR] Error: Pages only supports files up to 26.2 MB in size...

C

Cyb3r-Jak3•6/24/23, 12:31 PM

Pages is trying to upload the cache folder which is too big. At the end of your build script add

&& rm -rf cache/

&& rm -rf cache/

&& rm -rf cache/

&& rm -rf cache/

B

Bink•6/24/23, 2:44 PM

Thanks for your help

W

Walshy•6/24/23, 7:56 PM

What's your account ID?

WWalshy > put: 'Value length of 39837727 exceeds limit of 26214400.'

W

Walshy•6/24/23, 8:05 PM

Same as last time, the worker bundle being uploaded is massive

Aavl Ok thanks for confirming, this time I saw that almost all the files/functions up...

W

Walshy•6/24/23, 8:40 PM

I'd make an issue on

next-on-pages

next-on-pages

- https://github.com/cloudflare/next-on-pages/issues

I filed an internal ticket for this issue too which you can reference: PAGES-2748

ي

يزن•6/25/23, 7:15 AM

I'm getting the EPIPE error on arch i have everything installed clang llvm libc++ lld python python-distutils-extra but I'm still getting it

/home/yzn/projects/test/node_modules/wrangler/wrangler-dist/cli.js:30632
            throw a;
            ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:5125:26)
    at async #assembleAndUpdateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:9140:23)
    at async #init (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:8902:5)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

/home/yzn/projects/test/node_modules/wrangler/wrangler-dist/cli.js:30632
            throw a;
            ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:5125:26)
    at async #assembleAndUpdateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:9140:23)
    at async #init (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:8902:5)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

/home/yzn/projects/test/node_modules/wrangler/wrangler-dist/cli.js:30632
            throw a;
            ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:5125:26)
    at async #assembleAndUpdateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:9140:23)
    at async #init (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:8902:5)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

/home/yzn/projects/test/node_modules/wrangler/wrangler-dist/cli.js:30632
            throw a;
            ^

Error: write EPIPE
    at afterWriteDispatched (node:internal/stream_base_commons:160:15)
    at writeGeneric (node:internal/stream_base_commons:151:3)
    at Socket._writeGeneric (node:net:930:11)
    at Socket._write (node:net:942:8)
    at writeOrBuffer (node:internal/streams/writable:392:12)
    at _write (node:internal/streams/writable:333:10)
    at Writable.write (node:internal/streams/writable:337:10)
    at Runtime.updateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:5125:26)
    at async #assembleAndUpdateConfig (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:9140:23)
    at async #init (/home/yzn/projects/test/node_modules/miniflare/dist/src/index.js:8902:5)
Emitted 'error' event on Socket instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}

with this command wrangler dev src/index.ts

ي

يزن•6/25/23, 7:37 AM

never mind after running this command it works now

yay -Sy extra/libc++ aur/llvm-libunwind

yay -Sy extra/libc++ aur/llvm-libunwind

yay -Sy extra/libc++ aur/llvm-libunwind

yay -Sy extra/libc++ aur/llvm-libunwind

V

vvo•6/27/23, 1:42 PM

Hey there, it doesn't seem possible to use

unstable_dev

unstable_dev

and pass local: false in wrangler 3.x. Whatever I try, it will still default to local: true because the code checks for args.remote only. Which probably doesn't make sense given

unstable_dev

unstable_dev

doesn't allow setting remote: true. Any idea?

A

Aster•6/28/23, 3:00 PM

Hello there

, I posted in another channel but I think this one makes more sense

In our current workflow we deploy workers with a first

wrangler secret:bulk

wrangler secret:bulk

wrangler secret:bulk

wrangler secret:bulk and then a

wrangler publish

wrangler publish

wrangler publish

wrangler publish
But it generates a ton of deployments (1 deployment for each secret uploaded), making it hard to rollback in an automated fashion
Any tips on how to group secrets upload + publish as one deployment

? (wrangler v2)

J

James•6/28/23, 3:11 PM

As far as I know, this just isn't possible today and you'll always end up with multiple deployments as there's no back-end route that supports mass-putting, or retrieval of secrets.

A

Aster•6/28/23, 3:14 PM

Ah :/ So no way to check if a secret exists first either to skip the upload

Is there a way to query more than 10 deployments with

 yarn wrangler deployments list

yarn wrangler deployments list

 yarn wrangler deployments list

yarn wrangler deployments list? Then I could filter only the

Source:        Upload from Wrangler 🤠

Source: Upload from Wrangler 🤠

Source:        Upload from Wrangler 🤠

Source: Upload from Wrangler 🤠 to get real deployments

J

James•6/28/23, 3:18 PM

I don't believe so

W

Walshy•6/28/23, 3:21 PM

(cc: @admah - I expect this is not expected behaviour)

A

Aster•6/28/23, 3:57 PM

Just to bring more clarity on the subject: My goal would be to run a deployment from our CI/CD, monitor the error rate/latency for few minutes, then rollback in case of failure (hence the need for the list of deployments to be able to run

wrangler rollback <ID>

wrangler rollback <ID>

wrangler rollback <ID>

wrangler rollback <ID>)
(Our app using workers have a tight SLO, in case of problems a manual PR and rollback might be too slow and error prone)

0

0xAlche•6/29/23, 6:40 AM

Hi, I am currently hosting my project using cloudflare but I got stuck in issue there
The problem is related to DNS setting. I have already create CNAME record and redirect my main domain to the netlify url where react frontend is hosted so when I type main domain, the page is shown. Then, I created subdomain in cloudflare in A record and redirect it the Debian 10 vps ip address where the node backend is running on 3306 port. When I send request to the ip address, I get response. but in case of sending request to the subdomain, there is no response.
I don't know what's wrong with it. Any help and suggestion would be really appreciated. If you need more info regarding the issue, plz feel free to ask me. Thanks

U

Uneasy•6/29/23, 7:47 AM

so is there a solution for WSL2 wrangler 3 dev ?

Error: write EPIPE

Error: write EPIPE

Error: write EPIPE

Error: write EPIPE still occurs, even after installing some mentioned packages

M

matt•6/30/23, 2:13 AM

is there a way to inherit all environment variables when using

wrangler dev

wrangler dev

- currently finding that I need to write a lot of

--var X:$X --var Y:$Y ...

--var X:$X --var Y:$Y ...

--var X:$X --var Y:$Y ...

--var X:$X --var Y:$Y ...

Mmatt is there a way to inherit all environment variables when using `wrangler dev` - ...

C

Cyb3r-Jak3•6/30/23, 2:22 AM

Wrangler will read from

wrangler.toml

wrangler.toml

for

wrangler dev

wrangler dev

and you can use a

.dev.vars

.dev.vars

.dev.vars

.dev.vars file

M

matt•6/30/23, 5:48 AM

I'm trying to build a local dev environment, and managed to get wrangler dev working for a single script, but I now need to recreate the prod-like routes with multiple scripts. Does wrangler dev support running multiple scripts, each with its own route, e.g.

my.local/foo/* -> scripts/foo.js

my.local/foo/* -> scripts/foo.js

my.local/foo/* -> scripts/foo.js

my.local/foo/* -> scripts/foo.js

my.local/bar/* -> scripts/bar.js

my.local/bar/* -> scripts/bar.js

my.local/bar/* -> scripts/bar.js

my.local/bar/* -> scripts/bar.js
etc...

the only idea I have so far is to do the routing myself, where the handler will:
- check for presence of matching script
- start the wrangler dev process, incl port selection
- proxy the request through to the associated process/port
- use a process manager to kill process after idle timeout

M

matt•6/30/23, 6:26 AM

Ah it looks like I may need to use miniflare directly?

M

matt•6/30/23, 7:37 AM

i tried using

workers

workers

workers

workers but couldn't get live reload working... plus the contents of /scripts/ can change during development, so what I ended up with is not perfect but it's good enough for local dev:

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

app.use('/:name/*', async (req, res) => {
  const mf = new Miniflare({
    scriptPath: `./scripts/${req.params.name}/index.js`,
    bindings: process.env,
  })
  const url = `http://localhost:8787${req.originalUrl}`
  const queryRes = await mf.dispatchFetch(url, {
    method: req.method,
    headers: req.headers,
    body: req.body,
  })
  res.send(await queryRes.text())
  await mf.dispose()
})

Original message was deleted

M

MrBBot•6/30/23, 12:43 PM

Hey!

Unfortunately Miniflare doesn't implement the S3 API for R2, so you'll only be able to upload via the worker bindings locally.

Original message was deleted

M

MrBBot•6/30/23, 12:44 PM

We haven't implemented support for using remote R2 buckets in local mode. We had previously implemented this for KV, but it was incompatible with some changes we made to Miniflare's storage system. We may consider adding this back in the future.

M

MrBBot•6/30/23, 12:45 PM

If you need access to production data, you're best bet for now is to use

wrangler dev --remote

wrangler dev --remote

.

W

Walshy•7/1/23, 8:28 PM

Vitest and unstable dev is still the way

V

vassbence•7/1/23, 10:07 PM

How does the team feel currently about the --local, --preview and the --env flags? They can get quite messy

V

vassbence•7/1/23, 10:07 PM

KV doesnt work with --local, what does --preview do if I can use --env staging --env production etc

No, I mean that as a part of the build process for `wrangler`, Actions can pull the Zod schema, and

Similar Threads

Similar Threads

Similar Threads