🆕 The URL Pattern API is Newly Available! Use it to match and extract parts of URLs, no need to reinvent routing logic. Supports literals, wildcards, named groups, and even regex constraints. Learn how it works 👇 developer.mozilla.org/en-US/docs/...

We've released an ESLint and OXLint plugin for preact-signals, most of the current rules are footguns we have fallen into ourselves or have seen the issue often. Go try it out! github.com/preactjs/sig...

It has been ~173~ 0 days since a service worker got stuck & continually served outdated content. I want to like service workers, and I'm sure this particular situation is user error, but they seem to always fall far short of what I hope for every time I reach for one.

There's currently a bot that's mass opening issues & PRs shilling Hostinger and claiming to be not a bot, but an employee: github.com/agneliutkiene It was hard not to see this as the end result of LLM mania, but still, it's disappointing & is only going to get worse. Bots will run rampant.

Current side project I'm working on has built up 14 different `.safari-x-is-bad` classes with hacks to work around their divergent behavior. All are things the Safari team has refused to align on too so I guess I'm stuck with this forever; this is the state of the web when monopolies are allowed.

It's been really liberating finding good time slots to work on Preact and its ecosystem. Some of the recent things that came to be

👋 my recent contracts have ended (and my buffer’s running a bit thin) so I’m looking for what’s next spent the last year focused on OSS work, which I’ve loved, and now open to new opportunities! if you’re looking for a dev, pls to reach out! I've shared more about how I work below 🫡

What are people missing in Preact? I have been going out of my way to provide libraries where I can to help people get unblocked.

Is Safari ever going to stop requesting `apple-touch-icon-precomposed.png`? It has served no purpose since iOS 7 but to this day, if you open the 'Share' menu, Safari will blindly request it. I feel like that can be trimmed out now.

All this interop stuff with scroll events, scroll snapping, etc. Think someone could sneak in a fix for locking body scrolling on ios? github.com/adobe/react-... Look at `usePreventScroll` from React Aria which is probably one of the most robust solutions...like how is this still a problem...

Twice a year I get contacted by someone who believes they've solved open source funding. It's usually a new app or licensing scheme. Both miss the point. Most companies see sponsoring open source as "charity" or an unnecessary expense, and until that changes, no solution will make a difference.

Woke up this morning to a dozen notifications from @jovidecroock.com advancing @preactjs.com & its integrations. He’s often single-handedly pushing the ecosystem forward and I wanted to show some appreciation on behalf of all users — without him, Preact would be no where near as successful.

to make a slightly grander statement, two things people should do more often: - read and write your own dependencies - vendor code rather than installing it from npm

Well, we shipped it! @preactjs.com is joining the party with an official @tanstack.com Query adapter 🎉 Huge shoutout to @thvdnta.bsky.social, who drove this effort 🙌 Welcome, @preactjs.com 👋

Models is worth calling out separately, it's something we introduced in signals to allow separating your logic from the view. preactjs.com/guide/v10/si...

Here is one of the dumbest things about vibe coding that I don't see a lot of people talking about Imagine you're an open source maintainer and someone opens up a pull request against your repository that they vibe coded. They may or may not tell you they vibe coded it; it doesn't really matter… 🧵

opening github links on mobile is exciting, it’s broken in a new and different way every single day now

I think it's time for unopinionated formatters to make a comeback. After quite a few years of reading code, most people will build preferences for how they structure certain things for better readability in the future; this is deeply subjective and we all differ to a sizable degree. Adhering

Blink: Intent to Prototype: Lazy loading for video and audio elements

The new update to signals-debug and the devtools now includes highlights of computeds/signals causing component re-renders! Play with it at stackblitz.com/edit/vitejs-...

Wanted to see whether preact could finally replace insertBefore with moveBefore but turns out... it's still broken issues.chromium.org/issues/45482...

Just a PSA: "muted" text colors should be used extremely sparingly for footnotes and asides on the web, it should not be the standard color for the entire site. When only the title of a page has passing contrast, the page becomes a mess of muddled grays with no obvious place for focus to land.

"SAFARIIII", he screams, after battling a bug (and the complete lack of visibility that Apple gives to iOS devices) that was caused by the lack of support for `requestIdleCallback`. It's only been 10 years guys, c'mon.

Droppin' this here for anyone else who has absolutely 0 interest in GitHub's new "Agents" tab added to the top of every repo: github.com/orgs/communi...

UI toolkits .. sometimes feel like having ultra processed food paulmakeswebsites.com/writing/shad...

I've never bumped treesitter without immediately regretting it. Whilst I'm appreciative of what those maintainers do, at least once a quarter my editor becomes unrecognizable and I have to decide to downgrade or spend hours clawing back my old config. Fundamental grammar shouldn't often change.

The debugging experience in signals should be great, I've been working a lot on it and I would like to share some first versions of the debugging improvements I've been working on. Feedback and contributions are always appreciated! jovidecroock.com/blog/signals...

64% of WebKit non-Apple contributions, 20% of Chromium non-Google, 27% of Servo, 39% of test262, and it goes on. And doing all this as a worker-owned, employee-run cooperative. The world would be a very different place if companies like Igalia were the norm rather than the exception in tech.

Released a new markdown rendering library for Preact called preact-md. It currently uses the general unified remark/rehype by default and sanitises inputs.

Some friction is healthy in our online interactions. You shouldn't be able to send a bug report without a reproduction. You shouldn't be able to create a PR without understanding the issue (and the solution). You should (try to) be aware of their context before replying to an unknown person online.

To recap, NPM allows 2FA TOTP token reuse within the token’s validity window. I reported this and was told it’s a “known low-risk issue” and that they “don’t consider this to present a significant security risk.” So, let’s look at how this seemingly small issue could be leveraged by a phisher. 1/

Just show the prompt and save us all time and resources. distantprovince.by/posts/its-ru...

The browser has everything you need, why not everything needs to be server-rendered and how preloading can alleviate complexity. jovidecroock.com/blog/platform

In SF for work and have a free afternoon & night (and might sneak away during this week too), anyone have recommendations?

From the thread: "Attacks from bot compromised Next.js assets spiked on 2025-12-05 from the usual 100 IP baseline to close to a 1000." If you're not 100% sure you're NOT vulnerable, you should patch your Next.js apps ASAP. And if you're 100% sure... patch anyway.

This is a new sort of post for me. Trust in OSS is a thing I care a lot about. This post is my attempt to frame AI slop PRs as an attack on trust in open source.

Finally got myself a KVM switch for swapping between my work & personal device and my god am I kicking myself for not doing it sooner. All monitors have kinda awful on-screen displays, with awkward controls to boot, but swapping display inputs was a ~40 second process with mine previously.

RSCs were a mistake. I went back to a client-side only solution using Preact for my latest project because the complexity you buy into is simply not worth the benefit of RSCs.

The changed code is a small fraction of an open source contribution. Your commitment to understand the issue, how your proposed solution fits with the project, and be ready to own and push the review process forward is the biggest chunk of the work. Your effort is the contribution, not the code.

Hello friends and welcome to a new “How is ESM vs CJS going!” 33.4% of the popular packages on npm now includes ESM. Up from 29.6% half a year ago. We have a third! ESM-only is up from 11.5% to 12.6%. This is also the impact of half a year of Node 18 being EOL, making `require(esm)` available

Firefox 147 is getting the Navigation API 🎉 🎉 🎉 See bugzilla.mozilla.org/show_bug.cgi...

If your business model doesn’t work without breaking the law, you’re not in business. You’re in organized crime.

Inspired by perfnow.nl, I've dusted off drafts of my network and device situation analysis. Good news/bad news: devices and networks are improving, but pages are swelling. The web is usable for the wealthy, but less so for everyone else. infrequently.org/2025/11/perf...

Wanted to write up a few quick slides for something, picked up a JS tool that I've heard a little about, and the default initializer crashed StackBlitz. Tried it locally just to see it attempts to load 150mb of JS. Nice Even after an hour of culling patches FF still struggles with the huge bundles

one downside of LLMs in OSS is _huge_ walls of text in issues, where the text does technically make sense but reads like a student trying to meet a character limit 😅

The GitHub PR “N hidden items, Load more…” UI is one of the *most* annoying things about its interface—and that says something! When I am working with a large, long-running PR (and yes, there are valid reasons for those!) I’d like to just be able to read the whole dang thing, please and thank you!

I stared into the abyss and 12MB of uncompressed JS, containing thousands of SVG icons, webpacked into cursed React components stared backed like a horrifying fractal of beady little eyes.

Remember that Intuit (the owner of Turbotax) lobbied extensively to kill Direct File, which did tax filing for free and somehow managed to make a good and intuitive user experience without AI.

My first advice to junior contributors is to STOP using vibe coding for PRs. OSS is always about people more than about code. We don't need more code generated by LLM, we need more people who care.

Vibe coding PRs - STOP please...