I needed a single component to look and behave identically in an Electron desktop app and a Next.js website. I thought sharing a component library would be the easy part. This talk is about what happens when CSS-in-JS meets a non-browser runtime — and how that constraint pushed me toward zero-runtime CSS, a three-layer token system, and a _hover API built entirely on CSS Custom Properties.
Speaker Bio
- Name: Soyoung Jung
- Mini-bio: Junior Frontend Engineer with a strong focus on user-centered problem solving, specializing in designing and implementing product features.
- Picture for slides:
- Would you like help with your presentation? Yes, please (Feedback on notes, practice run)
- Social media link(s): Linkedin
- Do you agree to the VanJS Code of Conduct? Yes
I needed a single component to look and behave identically in an Electron desktop app and a Next.js website. I thought sharing a component library would be the easy part. This talk is about what happens when CSS-in-JS meets a non-browser runtime — and how that constraint pushed me toward zero-runtime CSS, a three-layer token system, and a _hover API built entirely on CSS Custom Properties.
Speaker Bio