The Workers ran by DevProd (the team behind Wrangler) use promjs
The Workers ran by DevProd (the team behind Wrangler) use promjs
K
Ayou mean this one? https://github.com/weaveworks/promjs it is deprecated 
https://github.com/siimon/prom-client was so much simpler, but I wanted to give a try to otel to do kind of the same
https://github.com/siimon/prom-client was so much simpler, but I wanted to give a try to otel to do kind of the same
AI guess there is no shortcut to just experiment a lot 
no blog post/github code already ready to go ^^
no blog post/github code already ready to go ^^
L
need help
KThe API docs for that endpoint are just bad
LThank you. I will go and try it out right away.
Dhas anyone created a lib to parse xml in cf workers? i'm not familiar with HTMLRewriter and I don't feel like spending a few hours trying to figure it out so I can parse XML data.
KKDoesn't need to be Workers specific
Uok how do you have negative requests per second though
Uoh nvm
Uim sorry what language now
Uim guessing it just auto returns false tho? lol
SThank you Erisa, I'll give it a shot!
MHey!
With
I can access it from the computer on which I started wrangler, but not from my phone... (i can access other ports, if I run a simple web server for example)
I tried upgrading/downgrading wrangler version, nothing changed.
Am I missing something?
With
wrangler dev --ip 0.0.0.0I can access it from the computer on which I started wrangler, but not from my phone... (i can access other ports, if I run a simple web server for example)
I tried upgrading/downgrading wrangler version, nothing changed.
Am I missing something?
ZFor example if I host an api for storage or whatever and someone abuses it will I be held liable or he
ZCuz I don’t want neither a ban from cloudflare nor a legal problem
ZI will respond of course
Syeah use regex. we do this in prod for sitemap parsing and it works flawlessly despite the fact people will reply to this saying you should never do it 
Dpretty sure we use HTMLRewriter for parsing XML somewhere in our company
DSorry, what does generic mean? 
Ddon't they both return the same object?
Daren't they both an
anyisn't
res.json<T>()
HNo, it is providing that return type directly
Umight as well be the same though tbh its not like generics guarentee the type 
HNot always, but they can
HDepends on what they are being used on
UI mean for this specific example it will never. But generics are nice for a lot of cases yes
HFor example, you can use a Zod type in a generic, and then you are guaranteed that they match
AYou would use something like Joi to validate the input JSON, then casting would be type safe
AAnd it makes nice user errors that you can return in your 400
DI'm running my worker locally with
Am I doing something wrong here?
yarn wrangler dev --node-compat however I still get the error there are no matching exports even though they should be supported according to the docs (https://developers.cloudflare.com/workers/runtime-apis/nodejs/crypto/)Am I doing something wrong here?
AI had a similar issue with
crypto.randomUUID()Aimport crypto from 'node:crypto'; does not workAThere is a default
crypto.randomUUID() and crypto.getRandomValues() in the Worker runtime, I ended up using that even though it may not be 100% node compatible
HDid you enable the
nodejs_compat flag?HWhat you are showing is
--node-compat, which is the old polyfill methodHIt has support for less stuff
H
DThat fixes my example code but I'm working with a third party library which no longer works when using
nodejs_compat because it imports crypto instead of node:crypto. Is there some way I can make this third party library use the polyfill modules?HHRename
crypto to node:crypto, then mark it as externalDThat might work, but it seems a little weird to me that this is the best way to do it when
--node-compat worked out of the box. Is this really the way to go when using any third party library that uses node modules?HMaybe? I generally just avoid deps that require Node, but I know that isn't feasible for everyone
HDon't remember the exact reasoning for it, but iirc it was something about Node's APIs not being JS-standard, so they wanted to scope them
HJust like how non-standard Cloudflare APIs that require an import are scoped
cloudflare:KGiven there’s 4,521 dependents on the “crypto” lib on npm (which is built into Node now, yes) still 
