Grilled Cheese

ExploreLog inSign up

Alexander Lichter

@thealexlichter.com

742 Following6.4k Followers

🧡 Engineer @cloudflare.social
🎬 Video Content https://lichter.link/yt
💚 @nuxt.com team
🕰️ prev. DevRel @voidzero.dev

PostsRepliesMedia
@vite.devOct 12, 2026, 9:16 AMReposted by @thealexlichter.com

We've published multiple advisories affecting the dev server. The main one is an arbitrary command execution when using some editors or through `launch-editor` on Windows. Update now to the patched versions: - Vite 8.3.3, 8.2.4, 8.1.6, 7.3.7, 6.4.4 - Vite+ 1.1.0 Links to each report below.

@danielroe.devOct 8, 2026, 6:08 PMReposted by @thealexlichter.com

this kind of detailed analysis of something like an error page is _invaluable_

thank you @hugorcd.com! 🙏

btw, `my-bad` is an open, shareable project - it is designed to be useable by anyone, not just @nuxt.com!

npmx.dev/package/my-bad

HHugo@hugorcd.comOct 8, 2026, 6:04 PM

We made Nuxt’s error page clearer, with @danielroe.dev

Before and after the same Nuxt development error. Nuxt 4.5.2 gives the generic heading ‘An error has occurred’; the current my-bad renderer in Nuxt 4.6 puts ‘Cannot read properties of undefined (reading name)’ first, followed by the failing expression. Notes explain the clearer starting point and expanding callers or component ancestry when needed.Two views of the same failing frame. Original TypeScript points to shared/directory.ts:8:20; compiled JavaScript points to 4:18. Annotations explain how the highlight and caret locate the expression, source maps connect generated code to TypeScript, file actions open the editor, and copy location shares the precise position. Editor links retain the original source target.Application callers, optional framework frames and component ancestry in the current Nuxt development error renderer. Notes explain tracing the call that supplied the arguments, hiding library internals while following application code, preserving frame order, revealing framework detail for library debugging, and opening a captured component source file. Execution and UI hierarchy answer different questions.The Copy error split button and its menu. The primary action copies the diagnosis and source for an issue. Named menu choices offer Markdown, a prompt giving an agent the task and error context, or structured JSON for scripts and tools. All formats use the same report. Purple annotations explain each format’s purpose without covering the controls.
npmx.devmy-bad - npmxBeautiful dev-server error pages: HTML, ANSI and JSON from one sourcemapped report
5
@43081j.comOct 7, 2026, 12:55 AMReposted by @thealexlichter.com

ESLint jumped in install size by 2MB recently from a basic dependency update. Here's a short thread of the observations 🧵

@thealexlichter.comOct 6, 2026, 10:36 PM

Not ETA for template linting yet!

@voidzero.devOct 6, 2026, 12:03 PMReposted by @thealexlichter.com

Our Tales from the Void September 2026 Recap is out! 🌌

⚡ Vite+ 1.0 is out (free & OSS)
🧪 @vitest.dev 5, up to 50% faster
⏬️ @rolldown.rs can now reduce your number of chunks even more
📦 Updates on Bundled Dev Mode now runs the full @vite.dev playground suite
🎤 Less than 10 days to @viteconf.org

@thealexlichter.comOct 5, 2026, 6:23 AM

(Taking notes for `vp release`)

@typescript.fmOct 1, 2026, 2:49 PMReposted by @thealexlichter.com

Today on the pod: Type-aware linting with oxlint, Vite+ ecosystem, and the future of TypeScript dev tooling with VoidZero's Cameron Clark & Jim Dummett. Learn what's next for dev tools. share.transistor.fm/s/95684100 #typescript

@effect-ts.bsky.socialOct 1, 2026, 10:30 AMReposted by @thealexlichter.com

Effect v4 is here.

One ecosystem. Zero dependencies.

The next chapter of Effect and the foundation for building reliable software and AI agents in TypeScript.

Read the full announcement below:

effect.website/blog/release...

Effect 4.0 stable release announcement on a dark background. Large white “4.0” above “Production-ready. Out now.”  A timeline along the bottom progresses from 3.0 Stable to 4.0 RC to 4.0 Stable.
@thealexlichter.comSep 29, 2026, 6:57 PM

No, you need to set a flag to do so!

@thealexlichter.comSep 29, 2026, 7:01 AM

Don't get me wrong here. It is impressive to see what WASM can do but IMO this achievement is muddled with numbers that don't account for Oxc's raw transfer, and you should know better than that as someone who is doing benchmarks regularly (and comments on others). I am really disappointed Pooya...

@thealexlichter.comSep 29, 2026, 7:01 AM

Both the transformer benchmark and the parser benchmark show that Oxc is in the lead (on the tested fixtures). It is always the same with these benchmarks if they are not cross-checked. Why not reaching out to the team before sharing these numbers or just send a DM?

@thealexlichter.comSep 29, 2026, 7:01 AM

We at @voidzero.dev put a lot of work into benchmarking our tools correctly, so a simple PR to our benchmarks would have done the trick too!

github.com/oxc-project/...

github.com/oxc-project/...

@thealexlichter.comSep 29, 2026, 7:01 AM

The benchmark gives a misleading picture of Oxc It is not even considering Oxc's raw transfer (which makes Oxc significantly faster). Passing only lang (so not testing source maps, targets etc) should also be mentioned.

@thealexlichter.comSep 28, 2026, 3:01 PM

Time flies! @voidzero.dev joined @cloudflare.social 4 months ago. Since then, *so much* has happened.

So for everyone wondering how it is going, read @evanyou.me's blog post 👀

blog.cloudflare.com/voidzero-upd...

@thealexlichter.comSep 28, 2026, 9:09 AM

Vite+ reached stable 1.0 If you didn’t try it out yet, NOW is the best time 🔥

VVoidZero@voidzero.devSep 28, 2026, 7:24 AM

Vite+ 1.0 is here 🚀 A single `vp` CLI for managing your Node.js runtime, package manager, and frontend toolchain. Built on top of Vite, Vitest, Rolldown, Oxc, and tsdown. All with a single config. Free and open source under the MIT license. Start with `vp create` or migrate with `vp migrate`.

voidzero.devAnnouncing Vite+ 1.0Vite+ 1.0 is here. One CLI manages your runtime, package manager, and frontend toolchain.
2
@thealexlichter.comSep 26, 2026, 10:11 PM

👋

@thealexlichter.comSep 26, 2026, 6:17 PM

Can’t wait to get to that point!

@43081j.comSep 24, 2026, 6:23 PMReposted by @thealexlichter.com

Today we're launching ai-policy.dev!

A collaboration of me, @danielroe.dev and @matteogabriele.npmx.social - this provides a few human curated AI contribution policies you can choose from.

Our hope is that this will help you better define your stance and what kind of contributions you accept 🙏

ai-policy.devAI Contribution PoliciesReady-to-use AI contribution policies for open source projects.
13
@thealexlichter.comSep 25, 2026, 6:19 PM

Lovely idea! ✨

@programmier.barSep 15, 2026, 9:12 AMReposted by @thealexlichter.com

Bundler, Linter, Formatter, Testrunner, Package-Manager: Vite+ holt alles unter eine CLI.
Alexander Lichter aus dem Vite+-Team spricht mit uns über die Architektur, AI-Agents und erzählt, warum aus der Unternehmenslizenz eine MIT-Lizenz wurde.

Hier hören: www.programmier.bar/podcast/deep...

Older posts
Terms of UsePrivacy PolicyCommunity StandardsHelpGet the app

Grilled Cheese is a product of Village Compute

Version devBuilt at: 2026-10-12 04:31:30 EDT