Norbiros

Norbiros

@norbiros.dev

OSS developer in the wild // https://norbiros. dev

40 followers72 following32 posts

Change my mind: there's no better stack than Vite+ (build/test/lint/fmt), pnpm, and @danielroe.dev's uppt (releases + staged trusted publishing) for developing and safely shipping Node/TS libraries.

Building LEGO while listening to good music and watching your agents actually get things done has to be one of the best feelings.

Nuxt 5 still has a long way to go, but early benchmarks on my fairly medium size app look very promising. Build time dropped from ~33.2s to ~17.8s: about 46% faster. Take these numbers with a big grain of salt, since it is still in development, but let's hope we can push it even further.

My email inbox is constantly flooded with emails about new AI features and random sales pitches. It is genuinely refreshing to get one from "Piotr from Blacksmith" saying my GitHub Actions are getting faster for free - and I don’t need to do anything.

I’ve just migrated the documentation for `nuxt-open-fetch` and `@norbiros/nuxt-auto-form` to Docus. It means I now get some great features out of the box, less boilerplate and easier-to-maintain documentation. annd I may also contribute a few improvements back to docus!

Did you know that GitHub Actions now supports the `parallel` keyword? I was waiting for something like this for sooo long! And I only found out about it thanks to PRs opened by @luc122c.bsky.social for Nuxt, Nitro, and other big projects in the ecosystem.

I’ve published my first Vue RFC, proposing a parser-agnostic AST contract for Vue. The goal is to make it possible to replace `@babel/parser` with parsers such as Oxc or Yuku in the future 👀 If you have any feedback, it would be greatly appreciated! github.com/vuejs/rfcs/d...

github.com[RFC]: (TS)-ESTree-compatible AST for compiler APIs · vuejs rfcs · Discussion #835Start Date: 2026-07-20 Target Major Version: 4.x Reference Issues: N/A Implementation PR: NoteI am not a member of the Vue team, nor am I an expert in Vue's compiler, ESTree, or the parser implemen...

I wonder whether ESLint/Oxlint should show rule documentation links to agents that invoke them (fe. a website/markdown). It would help agents understand complex rules better, but it also creates a real prompt-injection risk.

It’s still possible to do this through the JSON formatter. And if you’re running in manual mode, you’ll probably need to accept a query or wget command, but still I'm unsure about that

You are up to date.