why do I get the feeling that they’re starting to hard-code answers to these common tests in newer models
In reply to Mastodon post
A versioned archive of posts from Bluesky, Mastodon, GitHub, npm, YouTube, Letterboxd, Hacker News, and blogs. Browse the most popular posts.
Last built .
| Since | posts | replies | likes | reposts and quotes | views | |
|---|---|---|---|---|---|---|
| Bluesky | 1,039 | 8,236 | 23,127 | 2,380 | ||
| Mastodon | 2,399 | 29,156 | 55,396 | 16,820 | ||
| GitHub | 179 | 5,777 3,520 | 33,866 | 3,317 | ||
| npm | 139 | 1,546 | 75,991,720 | |||
| YouTube | 30 | 1,203 | 32,713 | |||
| Letterboxd | 55 | |||||
| Blog | 20 | |||||
| Hacker News | 59 | 575 | 802 | |||
| All | 4,807 | 37,967 | 114,394 | 22,517 | 76,024,433 |
why do I get the feeling that they’re starting to hard-code answers to these common tests in newer models
is this stuff getting better or no

follow me for incredibly controversial and spicy takes on software development
if you want stable and reliable software, give developers stable and reliable employment
a reliable source has relayed that perhaps the flight attendant in fact said “infant life vests” which, in fairness to my ego, seems equally implausible
look, as my own internal dialogue has surmised: no aircraft can contain an infinite number of life vests. that would be silly. anyone would be silly to think that. the flight attendants did not announce that as part of the safety briefing…
when VC funded projects quiet-quit
A look back at the year of 11ty, 2025 edition (№8):
+73% releases (×177)
+15% issues closed (×804)
+51% downloads (4.7M)
-28% dependencies (×134)
-22% size (21 MB)
it clearly needs to be repeated that layoffs are a leadership failure, full stop.
a person who invented a toilet that can flush 50 golf balls watching a commercial from a company advertising a 60-ball flush: “well, shit”
I see a yearly recap blog post, I boost a yearly recap blog post. 💪
Got a new sign for my office for Christmas 🎄

just to be clear the pluribus hive mind is the borg with a smile
happy holidays
printed our holiday nativity scene this year 🎄

with a *huge* assist from Svelte’s https://www.npmjs.com/package/@sveltejs/acorn-typescript here
first draft of zero configuration typescript (with dependency mapping) in @11ty is working — weeeeeeeeeeee

software complexity sells via developer ego
happy holidays!
Just deleted a bunch of testing boilerplate in this repo after @vitest added `import.meta.resolve` support 🏆
I think https://github.com/zachleat/import-module-string is one of the best things I’ve built this year (even if no one else does 😅)
Writing database queries is too close to the metal. Best practices don’t work! It’s time to make SQL enterprise-scale with utility classes.
Curious how to use Node.js’s new Type Stripping feature for TypeScript compatibility with Eleventy? We have you covered: https://www.11ty.dev/docs/languages/typescript/#configuration
if you see https://scraper.buffer.com/debugger can you tell them I have beef with them
a one-way street can also be a two-way street with the right attitude
“a one-way mirror, also called two-way mirror…” — https://en.wikipedia.org/wiki/One-way_mirror
Watched 12 Angry Men last night and it had me wondering if it was legal in the USA in 1957 for women to serve on a jury — looks like it was state-by-state starting with Wyoming in 1870 all the way up to Mississippi in 1968.
CommonJS? ESM? TypeScript? Wait, even CommonJS TypeScript?? Eleventy can run them all.
https://www.11ty.dev/docs/cjs-esm/
Which should you choose? It depends! The social-media sized answer is: ESM 😅
leadership wants an everything app
users want an everything bagel
Tiny bug fix release of `<table-saw>`: https://github.com/zachleat/table-saw/releases/tag/v1.0.7
RE: https://chaos.social/@FlohEinstein/115727872442211456
Y’all are too wild 😅
👍✅ Runtimes supporting CommonJS and ESM
👎❌ Modules dual publishing both CommonJS and ESM
Deno both supports and absolutely does not support CommonJS 😅
1️⃣ https://docs.deno.com/examples/cjs_to_esm_tutorial/
2️⃣ https://deno.com/blog/commonjs-is-hurting-javascript
3️⃣ https://docs.deno.com/runtime/fundamentals/node/#commonjs-support

a dad hat that says “corny on main”
Currently wondering what it feels like to work so hard on an open-licensed typeface only to have it co-opted by very terrible and very famous people as part of their core brand identity.
Thankful to @jacklorusso for their 11ty docs contribution detailing how to use @deno_land’s new `dx` command with Eleventy: https://www.11ty.dev/docs/javascript-runtime/#deno
*gently opens up the December 15th flap on my react CVE advent calendar*
Coming to a canary near you: adding support for Node’s Module Compile Cache feature (existing Node 20+ minimum is unchanged but this is featured tested and available in Node 22.8+ only).
what if ___ (good thing) but instead, ___ (worse thing)
one of the 5 stages of grief is denial of service
ok fine but can react server components show emotional vulnerability too
Eleventy Core Dependency Watch (2025 Edition)
https://www.11ty.dev/blog/dependency-watch/
v4.0.0.alpha.6 (compared with v3) reduces:
1️⃣ dependencies 21.6%
2️⃣ 3rd-party dependencies 27.6%
3️⃣ node_modules weight 33.3%
is software getting better?
New core pre-release: v4.0.0-alpha.6
https://github.com/11ty/eleventy/releases/tag/v4.0.0-alpha.6
Note: this includes a new `@11ty/nunjucks` package.
I’d like to revise and say that my hotter take is that every VC-funded *open source* software project should report both runway amounts and how many active FTE they have on payroll
my hot take is that I think every VC-funded software project should report how much runway they have left every month
TIL about Carlito, a typeface (derived from Lato) made by Łukasz Dziedzic — the same type designer that made Lato!
Take my npm tokens, take my land,
Take me where I cannot stand.
I don't care, I'm still free,
You can't take the sky from me.
I wish dependencies would stop embedding their own arguments parser in a package that didn’t need a CLI to begin with.
Eleventy has *three* different dependencies with pretty hefty (and outdated) CLI argument parser libraries 😭
Is there an `overrides`-style feature that works for libraries? (afaik this feature is only for app-level code)
we have liftoff

you’re very popular on linkedin (DEROGATORY)
if you’re cold, your dependency is cold — bring them inside
I don’t know if this is a good decision but it also feels long overdue

Strangers by Spring is #BuiltWithEleventy by @henry and @redintheshell 🏆🏆🏆
She’ll never see this because she’s too healthy to be chronically online but I am so thankful to my partner — a genuinely incredible person that I am so happy and privileged to be married to for the last 16 years.
Every truly great thing I have in my life is because of her and every good thing I’ve been given credit for in my life is also because of her.
Only 34 years left until our 50th anniversary ❤️
New core pre-release: v4.0.0-alpha.5
Full release notes: https://github.com/11ty/eleventy/releases/tag/v4.0.0-alpha.5
tfw your web site is static

React has taken down Cloudflare twice now so is this a good time to talk about Enterprise scale or is it still too soon
if you look in the footer of https://blog.fontawesome.com/ and tap on the Font Awesome flag you’ll see a variant of this component made to work with Font Awesome icons (and reusing the colors from the header image of the blog post too: https://blog.fontawesome.com/blog-awesome-to-11ty/#colors) 🥰
📮🔒 New post on the blog:
Securely publishing our packages to npm
It’s decorative <snow-fall> season, friends: https://www.zachleat.com/web/snow-fall/
Maintenance update: to simplify our docs footprint (and in reaction to deployment retention policies), we will maintain historical versioned branches of our docs for *major* versions only:
https://v2.11ty.dev/
https://v1.11ty.dev/
https://v0.11ty.dev/
Previously hosted minor version subdomains (e.g. https://v0-12-0.11ty.dev) will redirect to their respective major version.
Appreciate y’all!
DNS stands for “DO NOT meSs with this or you’re going to have a bad time”
📮🔒 New post on the blog
No more tokens! Locking down npm Publish Workflows
https://www.zachleat.com/web/npm-security/
Includes a checklist of 8 important things you can do to improve your security footprint when using GitHub and npm.
For interested folks, here’s the React PR that fixes CVE-2025-55182 affecting React Server Components (CVSS 10.0 Critical Severity): https://github.com/facebook/react/pull/35277
Blog post: https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
> Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
TIL about https://jsx.lol/ from @db which seems to be carrying the torch forward from my blog post a few years back: https://www.zachleat.com/web/react-criticism/
I wanted to do this for an @11ty conference but haven’t had the bandwidth yet 🫠
Free idea:
A developer conference (née job fair) where all of the speakers are folks that aren’t employed and are looking! Speakers would really benefit from the authority that conference speaking provides and employers looking to hire can send their own devs in to learn (and recruit)!
As a security precaution I had previously configured every single 11ty repository to have its own single-package-scoped npm token (there were probably ~30 or so), so this is a lovely improvement 😅
This took a lot of tedious work but I’m now npm token free, weee!
The @11ty ecosystem is now using Trusted Publishers (https://docs.npmjs.com/trusted-publishers)

today I woke up excited to do business excellence
I have been informed (via email) that Zach Leat has been nominated for the Business Excellence Awards 2026 — please clap 😅
The @smashingmag Email Newsletter on Web Performance this week was great!
This year we’re thankful for everyone that took a few minutes to fill out our 8 question survey (with 5 multiple choice questions 😅).
If you haven’t yet, we are still accepting submissions! It will help us prioritize the future of our project! Appreciate y’all!
for black friday I took 20% of the words off of my blog but I won’t tell you which ones
Update: at time of writing Eleventy core (0.x, 1.x, 2.x, 3.x, 4.x prereleases) and our official plugins are still unaffected.
(Compromised package count was updated to 834 from 533 in the latest @SocketSecurity update: https://socket.dev/blog/shai-hulud-strikes-again-v2)
Is there a way to configure an npm package to *require* provenance and fail any publish attempts that don’t have it? I don’t think the Trusted Publisher stuff has that option, if I’m reading it correctly.
Was wondering how to use Subresource Integrity with dynamic import() — thought maybe there was a path forward using import attributes (no) but I did stumble across this excellent post about using it with Import Maps (from @guybedford):
How to hallucinate using Web Components https://www.zachleat.com/web/hallucinate/
participating in the JavaScript ecosystem continues to feel like living in a house that’s on fire and all of your roommates are just buying their own fire extinguishers and pretending that it’s just a temporary bout of really hot weather
There is an active npm security event: https://socket.dev/blog/shai-hulud-strikes-again-v2
At time of writing, Eleventy core and our official suite of plugins are unaffected.
The 80px vertical page shift from “This issue has been moved to a discussion” clunking in on an already loaded page may be my villain origin story.
Bring back toasts, GitHub! 🥸

I have elevated to a new plane of open source existence

Pretty wild that GitHub Contribution Graphs don’t count responding to or closing issues as Activity (though *opening* issues counts 🥸)
we are definitely triaging like we’ve never triaged before

SORRY FOR THE LATE RESPONSE.
APPRECIATE YOUR PATIENCE.
SORRY FOR THE RESPONSE.
APPRECIATE YOU.
SORRY, RESPONSE.
APPRECIATE.
SORRY.
this is using a <squirm-inal> Web Component from 2021: https://github.com/zachleat/squirminal/
2021-vintage Web Components are React 17-era. No big refactors or rewrites required.
went on a small side quest this morning and added an AI Mode toggle to my blog posts
e.g. https://www.zachleat.com/web/adventures-in-date-parsing/

Help guide the future of Eleventy by participating in the Eleventy Community Survey (and Suggestion Box):
we are really leaning into those outages today, huh https://www.githubstatus.com/
@bobmonsour is looking for feedback on https://11tybundle.dev/ — please participate in the redesign survey!
https://docs.google.com/forms/d/e/1FAIpQLSfef-ekQaPHSRnIQY8iUn-fmR79P1BXep-j2jPM3RKCDEcDnw/viewform
I can track web development eras like tree rings, but each ring is move-fast-and-break-things devs saying “we don’t care about Y and you shouldn’t either—here are a bunch of tools that disregard Y” and indie folks saying “no thanks, I do care about Y—those tools aren’t useful if they don’t take Y into account.”
Later it becomes “as an industry we have always thought Y was very important—we should build *new* tools that embrace Y, I wish someone would have said something before”
Rinse & repeat.
RE: https://infosec.exchange/@jerry/115571012524697515
we should have a cyber-monday-esque international holiday where we turn the web off for an entire day
you know what hasn’t taken down Cloudflare (afaik): dangerouslySetInnerHTML
did Cloudflare do another React useEffect
why is no one talking about the <fieldset> of zelda
TIL about the HTML Size Analyzer from DebugBear. Great for finding sneaky Data URIs or large payloads of JSON in your pages:
“are the devtools keeping pace with emerging web standards?” is a very good litmus test for whether a browser vendor is investing alongside the web or just treading water
Jeppe Reinhold was kind enough to share this tool from Craigory Coppola to compare popularity of different Major/Minor versions of a package on npm:
Shipped a tiny little breaking change to <browser-window> this morning to show the full URL in the URL-bar by default (with an escape hatch if you hate it)
Repo: https://github.com/zachleat/browser-window
Demo: https://zachleat.github.io/browser-window/demo.html
Now available in v2.0.0