I recommend Axiom, with the otel-cf-workers package you can add opentelemetry tracing pretty easily

D

DaniFoldiOP•1/5/24, 1:02 PM

(https://axiom.co)

DDaniFoldi I recommend Axiom, with the otel-cf-workers package you can add opentelemetry tr...

S

sathoro•1/5/24, 1:04 PM

ty! you actually recommended them several months ago for logging but I went with Datadog since they didn't have Logpush integration yet... looks like I might be able to fully migrate to them now

D

DaniFoldiOP•1/5/24, 1:05 PM

yes, they now have logpush integration that works will all cf datasets, which is cool

0

0xffb3•1/5/24, 3:23 PM

can i run python on workers?

C

Cyb3r-Jak3•1/5/24, 3:24 PM

Not easily. You’d have to compile your python script to WASM to be able to get it to run on workers

K

kian•1/5/24, 4:16 PM

Is this Miniflare 2?

K

kian•1/5/24, 4:16 PM

nodejs_compat modules are a Miniflare 3 thing

K

kian•1/5/24, 4:31 PM

Yeah, Miniflare 3 doesn’t have a Jest environment

P

Pato•1/5/24, 5:12 PM

Hey! anyone knows if i can use pg library in workers?

K

kian•1/5/24, 5:22 PM

With

node_compat = true

node_compat = true

node_compat = true

node_compat = true in Wrangler.toml, yes.

P

Pato•1/5/24, 5:26 PM

i have it like that but im still getting this error

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

EAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
        - install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "stream": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

ERROR in ./node_modules/split2/index.js 20:26-51
Module not found: Error: Can't resolve 'string_decoder' in '/Users/CockroachDB testing/cfw-ts-apiserver-template/node_modules/split2'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
        - add a fallback 'resolve.fallback: { "string_decoder": require.resolve("string_decoder/") }'
        - install 'string_decoder'
If you don't want to include a polyfill, you can use an empty module like this:
        resolve.fallback: { "string_decoder": false }
 @ ./node_modules/pgpass/lib/helper.js 5:12-29
 @ ./node_modules/pgpass/lib/index.js 5:13-35
 @ ./node_modules/pg/lib/client.js 229:23-40
 @ ./node_modules/pg/lib/index.js 3:13-32
 @ ./src/handlers/handler.ts 4:13-26
 @ ./src/routes/routes.ts 5:18-48
 @ ./src/handler.ts 9:33-59
 @ ./src/index.ts 3:18-38

K

kian•1/5/24, 5:38 PM

I've never seen this output before - what Wrangler version are you using?

P

Pato•1/5/24, 5:39 PM

wrangler 3.4.0

K

kian•1/5/24, 5:41 PM

That looks like you're using a custom build that calls Webpack or similar.

K

kian•1/5/24, 5:41 PM

Wrangler itself uses esbuild.

P

Pato•1/5/24, 5:42 PM

yes im using this :

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

"scripts": {
    "build": "webpack",
    "format": "prettier --write  '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "lint": "eslint --max-warnings=0 src && prettier --check '*.{json,js}' 'src/**/*.{js,ts}' 'test/**/*.{js,ts}'",
    "test": "jest --config jestconfig.json --verbose"
  },

S

subscriptions•1/5/24, 6:27 PM

Hey guys,
If we have a limit on number of invocations per day on the workers paid plan I will move almost all my workload to workers, and few of the developers I have talked to also said the same thing. How to raise a feature request for this? Also, curious why is it not present in paid plan when we have the limits on free plan if anyone could explain a bit further it will really help.

K

kian•1/5/24, 6:29 PM

I'm not sure what you mean by invitations.

K

kian•1/5/24, 6:29 PM

Do you mean requests?

S

subscriptions•1/5/24, 6:31 PM

Sorry updated it, I meant "invocations"

K

kian•1/5/24, 6:32 PM

You can't add a limit if that's what you wanted, you can only add a billing alert so you can go and manually remove the Workers from the routes.

S

subscriptions•1/5/24, 6:33 PM

Yeah, is there a way to request for this feature somewhere?

C

Chaika•1/5/24, 6:33 PM

Also, curious why is it not present in paid plan when we have the limits on free plan if anyone could explain a bit further it will really help

On Paid Plans you just pay for each request over the included amount.
You can't raise the free tier's included requests/day, other then by upgrading to Paid
https://developers.cloudflare.com/workers/platform/pricing/

Pricing · Cloudflare Workers docs

Workers plans and pricing information.

Ssubscriptions Yeah, is there a way to request for this feature somewhere?

C

Chaika•1/5/24, 6:35 PM

There's #workers-feature-suggestions or https://community.cloudflare.com/c/feedback/feature-request/30 on the community forums. I wouldn't hold out hope for it though, virtually no other CF Products have anything like that except Workers Free Tier.

For Standard Billing Model though you can add a CPU Ms Limit per request which can help cap things/make sure a Worker which normally is quick wouldn't take excessively long resulting in a big bill

CChaika There's #workers-feature-suggestions or https://community.cloudflare.com/c/feedb...

S

subscriptions•1/5/24, 6:37 PM

ok thank you

O

olup•1/5/24, 7:43 PM

Anyone knows the Mistral 7b rate limits on workers ai ? I can't find the info ?

D

docy•1/5/24, 9:03 PM

how much of a performance hit does

node_compat

node_compat

node_compat

node_compat incur?

D

docy•1/5/24, 9:03 PM

just because i am using

process.env

process.env

K

kian•1/5/24, 9:11 PM

Use

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"]

compatibility_flags = ["nodejs_compat"] instead

K

kian•1/5/24, 9:12 PM

It's modules added into the runtime rather than

node_compat

node_compat

node_compat

node_compat which is build-time polyfills.

Kkian Use `compatibility_flags = ["nodejs_compat"]` instead

D

docy•1/5/24, 9:58 PM

thanks!

Iiznak Hi I am on the free plan for workers which says i get 10ms of cpu execution time...

I

Isaac McFadyen•1/6/24, 2:17 AM

In general you are allowed short spikes above the 10ms limit, but you will run into issues eventually since the median CPU time being above 10ms suggests that eventually you will be limited.

I

Isaac McFadyen•1/6/24, 2:18 AM

The main solutions here are either to reduce your CPU time, if you can, or if you can't (e.g. hashing passwords, running expensive WASM) then you'll need to upgrade to the paid plan or just continue what you're doing (risking being throttled though).

U

Unsmart•1/6/24, 3:15 AM

The free plan never gets charged. If you were on a paid plan and had a limit set to 10ms you would still get charged the full amount of cpu you use afaik.

B

Beyondo•1/6/24, 3:20 AM

Guys, does turnstile requests consume the Workers' cpu time? Because I benchmarked, and found out that Recaptcha averages 300ms from Cloudflare's servers and sometimes less, whilst Cloudflare Turnstile averages over 400ms from Cloudflare's own servers, so I'm considering switching back to Google Recaptcha if Turnstile is gonna cost that CPU time per request

B

Beyondo•1/6/24, 3:21 AM

Or maybe there's a special way to use turnstile through workers that wouldn't cause that much verification time (like without http requests)?

B

Beyondo•1/6/24, 3:28 AM

Okay, I might be wrong, but quoting Cloudflare's docs:

CPU time is the amount of time the CPU actually spends doing work, during a given request.

Does that mean they won't charge for the time where a worker is "halted" (waiting for turnstile to respond)?

BBeyondo Okay, I might be wrong, but quoting Cloudflare's docs: > CPU time is the amount ...

C

Chaika•1/6/24, 3:32 AM

Yea, CPU Time doesn't include time you're waiting on responses from fetch requests, CPU isn't active

CChaika Yea, CPU Time doesn't include time you're waiting on responses from fetch reques...

B

Beyondo•1/6/24, 3:33 AM

Awesome, thank you!

D

Deo Kumar•1/6/24, 4:27 AM

https://developers.cloudflare.com/workers/runtime-apis/webassembly/javascript/#bundling

The documentation says we can import wasm binaries ending with

.wasm

.wasm

.wasm

.wasm or

.wasm?module

.wasm?module

.wasm?module

.wasm?module

But when I import using

.wasm?module

.wasm?module

.wasm?module

.wasm?module, it doesn't get resolved and throws exceptions.

Is there any mistake in documentation or am I doing anything wrong?

Wasm in JavaScript · Cloudflare Workers docs

Wasm can be used from within a Worker written in JavaScript or TypeScript by importing a Wasm module, and instantiating an instance of this module …

D

Deo Kumar•1/6/24, 4:30 AM

Or do I need to add

rules

rules

rules

rules for it in

wrangler.toml

wrangler.toml

file

D

Deo Kumar•1/6/24, 4:32 AM

In the documentation:

This is done using a ~default bundling~ rule which can be customized in wrangler.toml

0

0xffb3•1/6/24, 11:14 AM

love it

R

rec•1/6/24, 8:00 PM

is there a recommended way to handle multiple routes for a worker?
i'm trying to map out an integration i'm working on and not sure if it needs to be 1 worker per URL, or 1 worker per "area" (eg: auth, sales, webhooks), or can be 1 monolith worker - are there any limitations that might steer me to look a certain way?

E

Erisa•1/6/24, 8:10 PM

You can honestly do any of those approaches.
1 worker per URL: assign them routes like

domain.com/thisthing

domain.com/thisthing

domain.com/thisthing

domain.com/thisthing
1 worker per area: assign them routes like

domain.com/auth/*

domain.com/auth/*

domain.com/auth/*

domain.com/auth/*
1 monolith worker: assign them routes like

domain.com/*

domain.com/*

domain.com/*

domain.com/* or a worker custom domain

so it just depends on what makes the most sense for the dev flow that you want, and you can even have the workers communicate with each other over Service Bindings if need be (https://developers.cloudflare.com/workers/runtime-apis/service-bindings/#service-bindings)

E

Erisa•1/6/24, 8:11 PM

I suppose Workers for each route/path may be harder to develop unless theyre separate components that dont need to interact as a whole

R

rec•1/6/24, 8:22 PM

the monolith approach seems to be the sanest approach (well, until it's not)

i'm not too familiar with JS for server stuff, but is there any recommended approach to routing various endpoints for a worker? historically if i've needed an api written in js i'd just use express, but not even sure if that is an option for workers and if i google "cloudflare workers routing example" it doesn't seem to pull up what i'm looking for

I recommend Axiom, with the otel-cf-workers package you can add opentelemetry tracing pretty easily

Similar Threads

Similar Threads

Similar Threads