←back to thread

Vanilla JavaScript support for Tailwind Plus

(tailwindcss.com)
304 points ulrischa | 1 comments | 25 Jul 25 18:11 UTC | HN request time: 0.23s | source
Show context
paranoidxprod ◴[25 Jul 25 18:43 UTC] No.44686734[source]▶
Would love to know how they went about implementing these. I always find custom elements interesting. I know the guys over at data-star.dev used one to implement their inspector element, but unfortunately that is also behind pro.

I know Lit is used a lot but I’m always looking for new approaches.

replies(2): >>44686982 #>>44687120 #
1. WorldMaker ◴[25 Jul 25 19:12 UTC] No.44687120[source]▶
Since you are asking about other approaches, I've been doing some interesting and simple custom elements with my Knockout-inspired view engine [0]. I built an open source MPA application with a bunch of them [1]. I even gave a brief presentation on it [2] (each PR starting with #2 is a "slide"; I presented it in a "Presentation" profile for VS Code opening the numbered files in order, with the Live Preview extension side-by-side with a simple git alias to jump to "slide" merge commit based on PR number; I thought it went well to show off Developer Experience).

My biggest advice appears to be: remember that the Shadow DOM is optional.

[0] https://worldmaker.net/butterfloat/guides/web-components/

[1] https://github.com/WorldMaker/jocobookclub/tree/main/src/bf

[2] https://github.com/WorldMaker/butterfloat-presentation/pulls...