Jan Nicklas

@jantimon.bsky.social

living in Switzerland 🇨🇭 mainly working on typescript, css and compiler related frontend topics https://github.com/jantimon

@capt.dev hi I'm Jan frontend lead at Galaxus where we heavily use relay and relay is literally the last thing blocking us from going full ESM.. I'd love to work on the relay esm support myself just need your guidance to do it right could you please drop me a DM if you find some time?

I wouldn’t bet on 2025, but my hopes are high for 2026. Firefox has had an experimental implementation for years. Safari also has one now. And we’re implementing in Edge/Chrome. It’s a matter of agreeing on the spec now. Once done, it won’t take long for the feature to ship.

We're thrilled to announce the first stable release of Oxlint - version 1.0! Our Rust-powered JavaScript/TypeScript linter delivers 50~100x faster performance than ESLint with 500+ rules and zero configuration required. Time to give it a try! voidzero.dev/posts/announ...

Announcing Oxlint 1.0

The first stable version of Oxlint, a fast & easy-to-use Rust-powered linter for JavaScript and TypeScript, is out. Learn about its 50~100x speed advantage over ESLint, support for 500+ rules, real-wo...

voidzero.dev

Vite 7 (to be released in ~2 weeks) will be distributed as ESM-only, unblocked by require(esm). We decided to bump node versions to 20.19+, 22.12+ to have it unflagged. Here is @sapphi.red's PR removing the bits of CJS we were still shipping.

refactor!: bump required node version to 20.19+, 22.12+ and remove cjs build by sapphi-red · Pull Request #20032 · vitejs/vite

Description Built on top of #19972 Bumps required node version to 20.19+, 22.12+ so that we can remove cjs build. I haven't tested yet.

github.com

I ported React Router RSC Movies demo to Vite. github.com/hi-ogawa/rsc... RSC bundler feature is encapsulated in the package `@hiogawa/vite-rsc` and React Router RSC API integration is found in `./react-router-vite`. The latter part is mostly a copy of `parcel-plugin-react-router`.

GitHub - hi-ogawa/rsc-movies

Contribute to hi-ogawa/rsc-movies development by creating an account on GitHub.

github.com

Jacob@ebey.dev · last yr.

@scriptedalchemy.bsky.social and others who want a custom bundler integration take note, it's going to be easier than ever: github.com/jacob-ebey/p...

I just updated `react-server-dom-vite` PR with css import support github.com/facebook/rea.... I'm not sure if this is a right direction, but this seems to nicely handle css code split at each client reference level and it might potentially work as "framework-less" abstraction for Vite RSC.

feat: add react-server-dom-vite by hi-ogawa · Pull Request #33152 · facebook/react

Summary As a continuation from the discussion on Jacob's PR #31768, this is a new PR to add the react-server-dom-vite package and fixtures/flight-vite. To begin with, thank you to the React tea...

github.com

Lightning CSS v1.30.0 is released! 😀 ⚡️ Updated relative color spec for numbers and percentages ⚡️ Updated nesting spec for pseudo elements and interleaved rules ⚡️ Skip generating unnecessary @​supports ⚡️ Android support ⚡️ ... and more! github.com/parcel-bundl...

Released in 2.2.0-beta.2 and it's even smoother now! Here's comparison of latest Vitest on left vs beta on right. Flickering is gone and now you can scroll up to see results without scroll jumping. And of course there's the status summary of active test run on the bottom. github.com/vitest-dev/v...

AriPerkkio@ariperkkio.dev · 2y ago

Hello 🦋! Here's sneak peek into Vitest reporter improvements I've been working on for a while now. This reduces terminal flickering, fixes scroll issues and adds status summary. It's still WIP but looking really good so far!

CTA to Nav 🗺️ taking the CSS container query for stuck position: sticky elements for a spin 🔥 nav { container-type: scroll-state; } @​container scroll-state(stuck: top) { .nav__content { --expand: 1; } } trick here is to transition grid-template-columns with the custom property value to morph

Would you want core web vitals In Safari? Can you help me understand how you would use them and why numbers in one browser isn’t enough? (These may sound like silly questions, but I’d love to understand *your* specific context and use cases)