Hacker Newsnew | past | comments | ask | show | jobs | submit | niedzielski's commentslogin


you can try the --experimental-transform-types flag to support TypeScript code gen. I'll add it to the notes!

--experimental-transform-types: https://nodejs.org/en/blog/release/v22.7.0#experimental-tran...


I made a small template that demonstrates the new type-stripping feature in Node.js. Nothing fancy but I was surprised that I didn't need to install a TypeScript test runner and generally how nice it was.


Brave has a history of very concerning behavior: https://en.wikipedia.org/wiki/Brave_(web_browser)#Controvers....



good article. the point would have been more salient if the jimniels/html micro dependency had been inlined.


This is great! I would love to see time support. I always use Google Calendar or https://www.worldtimebuddy.com but each is lacking.


I agree. I had this same problem with a tree UI model. Each node had links to both the children and the parent. Mutating any node in the tree, changes the reference of that node. Mutating the linkage to the updated node cascades to every other node in the tree.


Thanks for sharing. Do you still implement your own designs or "throw it over the wall"? Any tips on making the switch?


That's interesting. I guess you miss out on batched rendering--if all your setters re-render, you might trigger multiple renders for a single logical update. If you're using signals, maybe you don't care as much about batched rendering. I would probably miss CSS selectors too.


Lit-html is so fast and cheap, batched rendering isn't really useful.

I will sometimes do a little trickery in my setters to prevent pointless server round-trips though.

The general rule of thumb with lit-html is "meh, just render. It's just a template clone, and pretty much free".

There's no need to miss css selectors, they work just fine. That's the advantage of avoiding shadow dom.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: