Nuxt 4.4 was released 1 month ago and hasn't seen a patch release?! is everything ok?
ok, I guess I’ll take this as a win for making our ‘every week or so’ patch an expected pattern!
this is basically a combination of a lot of conferences
… followed by me being on holiday. 🏝️
expect a release soon.
roe.dev/ama
#ama
my new website.. it will be web 2.0, indieweb, it will be peer2peer and e2ee, it will be PWA, it will be SSL, it will be decentralized, it will be like email, it will be RSS, webring, it will be 88 by 31, it will be web scale, interplanetary, it will be on the blockchain
#SteamTopSellers for week of 7 Apr — 14 April 2026 (No F2P):
#1 - Crimson Desert
#2 - Slay the Spire 2
#3 - Forza Horizon 6
#4 - Resident Evil 4
#5 - GUILTY GEAR -STRIVE-
steamdb.info/topsellers/2026W16/
When will Nuxt i18n with Vite 8 issue be fixed? Not only the i18n module, but others also have some issues with Vite 8.
my plan is to officially support vite 8 with the release of nuxt v5.
if modules aren’t compatible with vite 8, then please do open issues in their repos. having said that, vite 8 was _intended_ not to require any changes, however, so it might be a vite bug…
roe.dev/ama
#ama
@designdelve.bsky.social has released the long await FF7 🟢🔵⚔️ Design Delve episode.
It was a blast to watch it happen on twitch stream! 👷🐶
www.youtube.com/watch?v=kbNg...
#gaming #finalfantasyvii #ff7 #designdelve
I don’t disagree with the warning/PSA to users. I disagree with the comment “avoid all these apps”. Especially when I knew it was a honest first-time dev mistake. It feels more hurtful than informative.
The unfinished work wasn’t “released”. I think someone just found the lexicons on ufos
...we learned is that not only the scope is huge, but that most MF features inevitably live in the JS plugin layer and not the bundler.
Meanwhile, @gioboa.bsky.social had already shipped full Vite 7/8 support in module-federation/vite.
The Vite plugin is now the official recommendation for Module Federation with Vite!
github.com/module-federation/vite
What happened?
We spent months exploring built-in MF support in Rolldown, even reimplemented MF 2.0 from scratch for both Rolldown and Vite.
What...
Wasm GC is flipping awesome for JS interop.
If you have a complex object you want to return from a Wasm API, you just can.
The JS side can pass it back in calls Wasm functions to interact with it. The Wasm side can forget about it, and the GC will release it when the JS side is done.
In h3/crossws 0.4.5:
createWebSocketProxy
Use crossws server as a front. Buffers data during connection. Coming soon as a Nitro route rule and H3 utility.
fromNodeUpgradeHandler
Convert Node.js upgrade handlers into crossws. Enables easy SocketIO integration.
this is the only year we can get minecraft 26.7 please @mojang make it happen
enableGlobalVirtualStore was added in pnpm v10.12.1, and it is going to be even better once v11 is released. Thanks again for the pnpm lessons today, Zoltan. Here is the post he wrote about how the new global virtual store completely changes the way you can use git work trees.
new release of the @e18e.dev dependency diff action! 🚀
1.5.0 lets you report bundle size changes regardless of +/- and gives you a way to run the workflow without pr target
Introducing the Oxc Angular Compiler ✨
◆ 6.4x faster than Angular CLI
◆ 20.7x faster than Webpack
◆ First-class @vite.dev plugin with full HMR
◆ Built with Oxc
◆ Not another slop fork
While this is experiment, the @angular.dev team is looking into an Oxc integration.
voidzero.dev/posts/oxc-an...
`tsnapi` - a snapshot testing utility for the public API for library maintainers. Snapshots for both JavaScript and TypeScript declarations. It would help prevent unintended breaking changes on public API signatures.
Thanks @sxzz.dev for the initial idea and implementation.
github.com/antfu/tsnapi
That can't currently be represented in the data set. But the next release of yaml is indeed faster than js-yaml iirc so all should be fine
On now: Steam Hidden Object Fest! steamcommunity.com/gid/[g:1:27766192]/annou...
🆓 Graveyard Keeper is free to keep on Steam store.steampowered.com/app/599140/
We published three security advisories affecting the dev server.
Only apps using --host are affected.
Update now to the patched versions:
- Vite 8.0.5 / 7.3.2 / 6.4.2
- Vite+ 0.1.16
Links to each vulnerability report below.
Today on the pod: UUID fun, Cloudflare's EmDash WordPress replacement, OSS maintainer security, PerryTS native UI compilation, and Solid 2.0 deep dive. Plus Turborepo speedups & more! share.transistor.fm/s/026d8f55 #typescript
#SteamTopSellers for week of 31 Mar — 7 April 2026 (No F2P):
#1 - Crimson Desert
#2 - Slay the Spire 2
#3 - Resident Evil 4
#4 - Gray Zone Warfare
#5 - ARC Raiders
steamdb.info/topsellers/2026W15/
New Beta For Steam Workshop Browsing gamesteamcommunity.com/games/SteamWorkshop/anno...
Have you considered what looking for an indie game to play would look to someone who's never played anything besides yearly CoD releases? Steam bombards you with low effort clones, asset flips, 10/10 masterpieces that intentionally look like low effort asset flips as a meta-commentary.
Is it unfounded disdain, when it is a fact that if you open recent releases tab on Steam you'll see dozens of low effort deckbuilders? There are hundreds of technically indie developers who are just following whatever genre is popular right now hoping to catch a ripple in the pond.
- 51.9% fewer items scored: 122K -> 59K (-63K) - this is because we use your older likes as seed items and they are less likely to appear in the set of 200 most recent likes of your potential curators (we only consider 200 items max per curator).
If we are to launch this then we probably need to increase this 200 number.
- 0.4% fewer requests per user - this could be related to fewer items scored
- 1% fewer likes - which is interesting. I'm trying to reconcile with a larger number of "show more". Probably due to fewer items scored.
A settings control labeled "Seed recency min weight" with a value of 0.1. The description reads: "Reduces the influence of recent likes. The most recent like gets this weight; the oldest like gets 1.0; in between is linear. 0 = disabled, 0.1 = mild dampening (e.g. most recent like counts 10x less than the oldest)." Below the text is a line chart showing weight on the y-axis (ranging from 0.10 to 1.0) and time on the x-axis (from "recent" on the left to "older" on the right), with a straight diagonal line rising from 0.10 at the recent end to 1.0 at the older end.
I have not launched this fully yet and instead started another experiment which gives less weight to your most recent likes:
- give 0.1 to your most recent like
- 1.0 to your oldest like within 90 days window (max 500 likes)
- all other likes are linearly scaled
they call it "whole" milk when it's just 3.5%, curious
