It'll run with a max memory of 3MB so probably

Not sure there's a whole lot you can do about that

Might be an bug if it tries to load the entire thing when it doesn't match?

Without reading the code itself, I imagine it's probably loading attribute & value to run it's checks rather than differentiating between selectors that only care about the attribute vs selectors that care about attribute and value

but it's impossible to really work around that I guess?

if you receive

<div foo="bar">

you're always going to get

"bar"

or if you decide 'skip to the next element' when it hits

foo

then it'll have to parse

"bar"

to find the end of the element

> The tag scanner parses only the tag name and feeds it to the selector matcher. The matcher will switch parser to the lexer if there was a match or additional information about the tag (such as attributes) are required for matching.

That's interesting, I think actually most of the elements I'm interested in are tags. I could give it a quick go with a more specific selector and see if that solves it

Yeah - ideally it'll never read beyond

div

(and in this case, dying on the data attribute) if you don't have any selectors for the

div

tag

Hey guys! I'm working on my Worker app and I'm trying to connect it to my custom domain that is owned by my AWS account in Route 53. Is it true that there's no way to connect this domain to a CF Worker?

Seems to work, thanks a lot for the help. Will require some changes, but can definitely work with this.

I keep getting this error when using

wrangler dev

.

it also block all devices in LAN and make the internet super slow even on another devices 😐

Now I just can't use start dev 😐

Anyone happen to have an example of bringing in Buffer to a typescript project from node_compat without ignores or including all of node? Ex. https://blog.cloudflare.com/workers-node-js-asynclocalstorage/

// @ts-ignore
import { Buffer } from 'node:buffer';

The project is setup specifically for browser for the worker, trying to work out how I can bring in just node:buffer and its types without everything complaining.

Could you share your tsconfig?

My guess is the types aren't right

Got it in 1, added "@types/node" to the array and all errors went away.

Still getting used to typescript, thanks!

Dang, dies during the webpack build, more to figure out. :<

Unless you have a specific reason to use webpack, wrangler will just build it for you

Yeah, I use it for a few things and keep a base config around for special cases, it's not doing too much in this project so I could prob remove it, but I'd rather figure it out and keep it.

You'll have to tell it that

node:*

imports are external then

That worked

externals: {
    'node:buffer': 'node:buffer'
  }

What's the performance of cloudflare rust workers compared to javascript?

There will always be some performance hit for running wasm vs just running javascript. But for most applications, it should be negligible these days

What's the difference between Workers Custom Domains and Workers Routes?

Good question. Custom Domains are designed to manage the DNS, certs. etc for you, whereas with Routes, you have to configure the DNS yourself. https://developers.cloudflare.com/workers/platform/triggers/custom-domains/