Cloudflare has a thing called HTMLRewriter that is both a streaming HTML parser and selector for changing it. It's very efficient and let you change only the places you need.
For your example, you can just match in `[id^="insert"]` and add the actual firstName value in the handler.
I use it alot on the server side, but it's for JavaScript side, or Rust if you use the lower level lol-html.
+1 to the lol_html HTML rewriter. Basically you can give it a bunch of selectors and code that will do whatever with what is matching. It's very fast and quite nice. It has bindings to Lua and a few more, but not to Python.
The HTMLRewriter API is pleasant to work with. Bun has implemented it in addition to Cloudflare Workers. I would love for WinterCG to work on standardizing this API across JS runtimes so that I don't have to interact with lol-html across a WASM boundary in Node and Deno.
I wonder how useful this is to be placed inside a van for that tiny "bathroom" area. We drive most of the day so the clothes can be dry in there, if the energy usage is efficient.
Of course, clothes can be hung outside for the warmth of the sun, but this seems way cooler.
If you want something really efficient for clothes drying in a van or mobile home just place a small junkyard car radiator in that tiny "bathroom", and hook the radiator up to your engine's coolant loop.
As you're driving around your engine is already trying to vent heat to the outside, so you're mostly getting the heat "for free". The losses due to extending the coolant loop etc. will be comparatively minimal.
The only tricky bit will be carefully managing thermostats to ensure that radiator won't be melting something is the bathroom, your coolant will get hot enough to boil water.
A "it ain't dumb if it works" variant on that is to literally bolt a box to the top of your hood (depending on visibility etc.), then remove your hood's insulation, and possibly drill a hole to exchange air between the two. Anything in the "hot box" should dry as you drive around.
I was excited to use this in my Demo project, but `import from "node:@tailwindcss/postcss@latest"` throws error about the `exports` field in package.json.
With that aside, the blog post mentions not having to use `postcss-import` but it seems to include that as dependency. So we're still using `postcss-import`.
Coincidentally, I was just reading about how VSCode support WASM on their web edition[1] and this was mentioned in their effort to implement the Terminal.
I have always been fascinated by those sci-fi movies in which a person would swipe up on their tablet, and the current window would fly to another monitor.
The mbtiles have a different tag schema than the pbf (and they add layers and zooms). If/Once there is a widely used data conversion, there will probably be some centralized service providing it. But that doesn't solve your problem if you want a different schema.
