Unless there is/you can compile a WASM version, no

HHello, I’m Allie!Unless there is/you can compile a WASM version, no

what is that i never used those ? can you refer me some point to look after it cause i tried this

@cf-wasm/photon

@cf-wasm/photon

but was not doing what i wanted very less func as compare to sharp

SSatendra Singh what is that i never used those ? can you refer me some point to look after it c...

Hello, I’m Allie!OP•6/16/24, 10:54 AM

WebAssembly is a compilation target, like x64-darwin, that can be run in the Browser, and on platforms like Workers

Hello, I’m Allie!OP•6/16/24, 10:56 AM

It appears that while Sharp does support WASM, it also requires multithreading, which Workers does not support

HHello, I’m Allie!WebAssembly is a compilation target, like x64-darwin, that can be run in the Bro...

Satendra Singh•6/16/24, 10:56 AM

there was one i saw recently https://www.npmjs.com/package/@webassembly/sharp but i dont know this will work

npm

@webassembly/sharp

High performance Node.js image processing, the fastest module to resize JPEG, PNG, WebP, GIF, AVIF and TIFF images. Latest version: 0.31.3-blitz.4, last published: a year ago. Start using @webassembly/sharp in your project by running

npm i @webassembly/sharp

npm i @webassembly/sharp

. There are no other projects in the npm registry using @webassembly/sharp.

HHello, I’m Allie!It appears that while Sharp does support WASM, it also requires multithreading, ...

Satendra Singh•6/16/24, 10:56 AM

HHello, I’m Allie!It appears that while Sharp does support WASM, it also requires multithreading, ...

Satendra Singh•6/16/24, 10:58 AM

is workers are only who don't support or it whole serverless thing cause i saw some github repo who is using aws lambda which support sharp

SSatendra Singh is workers are only who don't support or it whole serverless thing cause i saw s...

Hello, I’m Allie!OP•6/16/24, 10:58 AM

AWS Lambda is something completely different

Hello, I’m Allie!OP•6/16/24, 10:58 AM

They might support it, idk

HHello, I’m Allie!They might support it, idk

Satendra Singh•6/16/24, 11:02 AM

actually i making a cdn type thing so needed sharp for that ,do you know anything which will help for this case

bennycondon•6/16/24, 12:54 PM

I remember seeing someone mention an undocumented flag which hides the version number from being printed for a wrangler command. Does anyone know what this flag could be?

SSatendra Singh what is that i never used those ? can you refer me some point to look after it c...

Satendra Singh•6/16/24, 2:54 PM

is there any thing which can just help me to change the img any formate to webp and dose littile bit of quality change , use this

 @cf-wasm/photon

 @cf-wasm/photon

didn't work good for my use case

SSatendra Singh is there any thing which can just help me to change the img any formate to webp ...

Hello, I’m Allie!OP•6/16/24, 2:55 PM

https://developers.cloudflare.com/images/transform-images/transform-via-workers/

Cloudflare Docs

Transform via Workers · Cloudflare Image Optimization docs

Using Cloudflare Workers to transform with a custom URL scheme gives you powerful programmatic control over every image request.

Ccoolio2244242 First Cloudflare project. I've been deploying a Pages app to a dev environment b...

coolio2244242•6/16/24, 7:29 PM

anyone with an idea on this? ^^

Walshy•6/16/24, 7:37 PM

answered in pages-helpDefining different Environments in wrangler.toml in Pages app

Murder Chicken•6/17/24, 5:46 PM

Is it possible to specify

--persist-to

--persist-to

wrangler.toml

wrangler.toml

to make it easier to share KV/D1 locally between two workers?

avsaase•6/18/24, 12:59 PM

Hi, is there a way to pass a default account to

wrangler

wrangler

when running commands? I have two accounts associated with my account (not sure what the correct terminology is) so when I run a command I get a prompt to select which one to use. I want to pipe the output into

jq

jq

but when I try that I get this error:

✘ [ERROR] More than one account available but unable to select one in non-interactive mode.

✘ [ERROR] More than one account available but unable to select one in non-interactive mode.

Aavsaase Hi, is there a way to pass a default account to `wrangler` when running commands...

Erisa•6/18/24, 1:13 PM

Set the

CLOUDFLARE_ACCOUNT_ID

CLOUDFLARE_ACCOUNT_ID

environment variable

avsaase•6/18/24, 1:21 PM

Perfect. Thank you!

John Kirkpatrick•6/20/24, 8:11 AM

I successfully uploaded a schema to the local D1 using:

npx wrangler d1 execute DB --local --file=./schema.sql

npx wrangler d1 execute DB --local --file=./schema.sql

But when I tried to upload my data the same way I just got the error response:
✘ [ERROR] statement too long
This worked fine with SQlite using

.read ./data.sql

.read ./data.sql

UPDATE:
I just realized I left off the

.sql

.sql

at the end. When it can't find the file name, it gives this cryptic error message which isn't in the docs.
I answer "y" to wranglers question if I want to report this as a bug.

mc-intosh•6/20/24, 7:56 PM

im trying to run

npm run deploy

npm run deploy

but every time i log in it just fails to get the response

JuanWTF•6/21/24, 4:32 PM

I'm having the same problem as @mc

mc-intosh•6/21/24, 4:34 PM

yeah so i've fixed it by running

npx wrangler login

npx wrangler login

and after that using

npx wrangler deploy

npx wrangler deploy

and it worked

JuanWTF•6/21/24, 4:36 PM

I tried that, but I got the same error when I tried to

npx wrangler login

npx wrangler login

mc-intosh•6/21/24, 4:36 PM

oh well you have to ping someone from cloudflare then

JuanWTF•6/21/24, 4:38 PM

@Cloudflare (Server Owner) is anyone else having this problem?

Vero•6/21/24, 4:53 PM

Hey, I haven't seen more reports but I'm passing this internally. I'll DM you

Vero•6/21/24, 4:53 PM

@JuanWTF

Kevin•6/21/24, 6:38 PM

Hey wrangler team... this is a crosspost from the DO channel, but I'm not getting responses there, and it may be a wrangler issue anyway:

I'm trying to republish an updated

itty-durable

itty-durable

that imports/extends

{ DurableObject }

{ DurableObject }

from 'cloudflare:workers'...

This works fine, and folks can use it downstream as long as they are using wrangler (obv), but I am unsure of how to add test coverage to this in a way that'll pass outside of a wrangler environment (e.g. jest/vitest on GH actions).

Any tips on how to pass this hurdle would be greatly appreciated!

Kevin•6/21/24, 6:39 PM

I currently get a failure to import, as one might expect:

 FAIL  src/IttyDurable.spec.ts [ src/IttyDurable.spec.ts ]
Error: Failed to resolve import "cloudflare:workers" from "src/IttyDurable.spec.ts". Does the file exist?

 FAIL  src/IttyDurable.spec.ts [ src/IttyDurable.spec.ts ]
Error: Failed to resolve import "cloudflare:workers" from "src/IttyDurable.spec.ts". Does the file exist?

Brendan•6/22/24, 1:07 AM

I just ran into this error without making any changes: ✘ [ERROR] Could not resolve "vitest/dist/suite-IbNSsUWN"

src/index.js:1:18:
1 │ import { a } from "vitest/dist/suite-IbNSsUWN";
╵ ~~~~~~

The module "./dist/suite-IbNSsUWN" was not found on the file system:

node_modules/vitest/package.json:37:11:
37 │ "./": "./",
╵ ~~~

You can mark the path "vitest/dist/suite-IbNSsUWN" as external to exclude it from the bundle, which will remove this error.

✘ [ERROR] Build failed with 1 error:

src/index.js:1:18: ERROR: Could not resolve "vitest/dist/suite-IbNSsUWN"

Brendan•6/22/24, 1:09 AM

wait nvm something weird changed

Deep•6/24/24, 4:32 AM

is this the right place a question about getting VSCode + Wrangler + Breakpoints to work?

Deep•6/24/24, 4:35 AM

i'm not sure what has changed but it was working fine for me for quite awhile... now i can't either 1) attach to wrangler and get it to actually break on a breakpoint (the VSCode editor shows the breakpoint is active but execution doesn't actually stop 2) if I run a launch.json with the following config, i get same behavior: VSCode hits the line as though a breakpoint is triggered but execution does not actually pause on the breakpoint...

Deep•6/24/24, 4:36 AM

{
"name": "Wrangler Dev Remote",
"type": "node",
"request": "launch",
"resolveSourceMapLocations": ["", "/node_modules/**"],
"program": "${workspaceFolder}/node_modules/wrangler/bin/wrangler.js",
"args": ["dev", "--inspector-port=59229", "--port=9999", "--remote"], //Force a high port to avoid conflicts with other debuggers
"attachSimplePort": 59229, //Matches --inspector-port above
"internalConsoleOptions": "neverOpen", // We want to see Wrangler's output usually so hide this
"console": "integratedTerminal", // Shows the wrangler output
"autoAttachChildProcesses": false
}

Deep•6/24/24, 4:37 AM

i'm trying to debug remotely as well. which, over the past several months, was working fine and was great... now...? maybe i'll try to install latest version of wrangler and see if that helps

Deep•6/24/24, 4:39 AM

Screenshot_2024-06-24_at_12.29.30_AM.png

Deep•6/24/24, 4:40 AM

this shows VSCode thinking it hit a breakpoint but in fact it didn't... i can't step, i can't inspect any variables and my postman request returns immediately with a response from my worker...

bnason•6/24/24, 1:05 PM

I'm trying to use

wrangler tail

wrangler tail

to get my projects logs but I get the error

workers.api.error.script_not_found [code: 10007]

workers.api.error.script_not_found [code: 10007]

My Nuxt app deployed fine and I am able to access it via the browser.

DDeep i'm not sure what has changed but it was working fine for me for quite awhile......

Deep•6/24/24, 1:33 PM

also... when I launch the remote dev configuration above wrangler will start to initialize, i can see my app controller starts and logs to console but then it immediately shuts down. so, honestly at this point, remote wrangler debugging is completely dead for me.... i've been using remote debugging for months and suddenly (past 2-3 weeks) it broke and isn't usable now. no clue why... hopefully someone at CF knows something...

bnason•6/24/24, 2:09 PM

So wrangler just made me go through the oauth process again, but now when I click Allow, wrangler throws an error.

SyntaxError: Unexpected token < in JSON at position 0

SyntaxError: Unexpected token < in JSON at position 0

Deep•6/24/24, 3:20 PM

ok, so here's what i've found in the wrangler logs that seem like it might be part of the issue...

--- 2024-06-24T15:16:57.498Z debug
workerd/util/symbolizer.c++:96: warning: Not symbolizing stack traces because $LLVM_SYMBOLIZER is not set. To symbolize stack traces, set $LLVM_SYMBOLIZER to the location of the llvm-symbolizer binary. When running tests under bazel, use

--test_env=LLVM_SYMBOLIZER=<path>

--test_env=LLVM_SYMBOLIZER=<path>

.
workerd/server/server.c++:3346: error: Uncaught exception: kj/compat/http.c++:2722: disconnected: worker_do_not_log; Request failed due to internal error
stack: 105a5edb0 106ec1420 105a60d90 105a60f4f 106ebcc1f 106ec1420 105a80138 1054158df 10513e5e8 10513e9f7 106ebcc1f 104fecf20 104aba5cf 105a8d26f 105a8e1d3 105a8eb93 105a565b8
workerd/server/server.c++:3346: error: Uncaught exception: kj/compat/http.c++:2722: disconnected: worker_do_not_log; Request failed due to internal error
stack: 105a5edb0 106ec1420 105a60d90 105a60f4f 106ebcc1f 106ec1420 105a80138 1054158df 10513e5e8 10513e9f7 106ebcc1f 104fecf20 104aba5cf 105a8d26f 105a8e1d3 105a8eb93 105a565b8

Deep•6/24/24, 3:22 PM

and not only that, the first errors i found in the wrangler logs was this one which i resolved/eliminated the error in the logs by creating dummy .env and .dev.vars files in my project...

--- 2024-06-24T15:14:44.307Z debug
Failed to load .env file "/Users/PROJECT_NAME/.dev.vars": Error: ENOENT: no such file or directory, open '/Users/PROJECT_NAME/.dev.vars'

Deep•6/24/24, 3:23 PM

anyway, i don't have time to debug this mess... i'm dropping remote debugging and working around the problem

Deep•6/24/24, 4:09 PM

well nevermind, i thought i could workaround this problem by doing local debugging... nope. no breakpoints get hit.... hopefully someone has a clue, i've exhausted all my options at this point and it's literally holding up a product launch

sethi•6/25/24, 5:28 PM

Hello all @Wrangler dev users! Over the last few months we’ve been working hard to refactor the internal implementation of wrangler’s dev servers. We’re really excited about the stability improvements this brings and the exciting opportunities it will unlock in the future! We’d love for you to give this a go on your Workers and let us know how it goes!

Try it out with the new

--experimental-dev-env

--experimental-dev-env

flag (shorthand:

--x-dev-env

--x-dev-env

) on wrangler v3.62.0 or newer:

$ npx wrangler@latest dev --x-dev-env
# or
$ npx wrangler@latest dev --remote --x-dev-env

$ npx wrangler@latest dev --x-dev-env
# or
$ npx wrangler@latest dev --remote --x-dev-env

If you come across any bugs feel free to create an issue at https://github.com/cloudflare/workers-sdk/issues/new. We’d also love to hear if it works for you without any bugs! We’ll be actively monitoring for these issues and feedback until July 8th before deciding to enable the flag by default.