patak.dev - Profile | ThreadSky | a Reddit-style client for Bluesky

TypeScript excitement 😉 Congrats to @searyanc.dev on landing big updates to the default tsconfig settings used by `tsc --init` 🎉 Defaults matter - and in TS 5.9 they embrace simplicity 💙 🔷 ESM (was CommonJS) 🔷 No down-leveling (was ES2016) 🔷 verbatimModuleSyntax: true github.com/microsoft/Ty...

submitted 14 hours ago • 6 comments

Today I reached big milestone at @neon.com We launched neon.new - a project that I've put a lot of effort into and I'm very proud of. I also got to the write the announcement blog post neon.com/blog/neon-launchpad And recorded a quick walkthrough of what it is: youtu.be/HU4k48jyOmo

submitted 1 day ago • 2 comments

My tool of the day - webcontainers.io

submitted 1 day ago • 0 comments

🎙️ So grateful to officially launch The Weekly Dev's Brew Podcast! To all the incredible guests who've already sat down with me @marktechson.com, @joshuakgoldberg.com @patak.dev @nearestnabors.com - thank you for your time and genuinely fascinating conversations.

submitted 1 day ago • 1 comment

We've added new coverage provider comparison page on Vitest documentation. This guide describes the lower level differences between Istanbul and V8. It should help users choosing which provider to use. vitest.dev/guide/covera...

submitted 1 day ago • 1 comment

React Router is now under an open Governance model Learn why and what that means for the future of the project

submitted 2 days ago • 0 comments

Double trouble! Today airs one of two Nuxt special episodes on DejaVue. Our guest is nobody else than @atinux.com, the creator of @nuxt.com and @nuxtlabs.com Together with hosts @michaelthiessen.bsky.social and @thealexlichter.com they talk about the origin of NuxtLabs and Nuxt, differences & more!

submitted 2 days ago • 1 comment

Truly honored to have @cloudflare.social backing @pkg.pr.new's data infrastructure!! Thanks to everyone involved!❤️

submitted 2 days ago • 0 comments

🎉 Tadaaa 🎉 vite-plugin-kit-routes 1.0 is out 🎉 A/ add the vite plugin B/ enjoy route typesafety ! Easy ?! More here: www.kitql.dev/docs/tools/0...

submitted 3 days ago • 3 comments

Another real world Rolldown-Vite performance win: @sanity.io studio’s build time went from: 21.9s to 5.1s (4.29x, w/o React Compiler) 49.6s to 20.0s (2.48x, w/ React Compiler)

submitted 3 days ago • 2 comments

Can @analogjs.org build @angular.dev dev apps with the latest technical preview of @vite.dev and @rolldown.rs? Yes 🤝 github.com/brandonrober...

submitted 4 days ago • 0 comments

This is huge! But don't take my word for it. Go try for yourself. Congratulations on an amazing release to @reinhold.is, @xeho91.dev and the whole storybook team.

submitted 4 days ago • 0 comments

I think the @storybook.js.org team wins the best major announcement page ever price. Stunning. And good that it is like that, because they moved mountains with this release. Kudos to everyone involved!

submitted 4 days ago • 2 comments

love seeing this visual. the storybook team have made such great progress, and we're so lucky to have worked with them on some of this stuff 💙

submitted 4 days ago • 0 comments

I am super proud of what we've built with Storybook 9, I truly believe it unlocks some new crazy good workflows. And just take a look at the gorgeous video and announcement page!! 💅🥳

submitted 4 days ago • 1 comment

So... I was working on making @pnpm.io a tad faster 😜 youtu.be/pNDFfJvaubY?...

submitted 4 days ago • 1 comment

🤯 each @vitest.dev release is spot-on on pain points. The low latency between the pain points appearing in the community and the solution landing in Vitest is outstanding

submitted 4 days ago • 0 comments

and alpha 1 is OUT! 🎉🎉🎉 not sure how much sleep there will be over the rest of the month 😆 (there's so much work still to do) ... but I could not be happier

submitted 5 days ago • 9 comments

AST based V8 code coverage is finally here! I thought of this feature first time over 2 years ago, but knew it would require so much work that I couldn't finish it by working on Vitest just on weekends. Ever since @stackblitz.com hired me to work on Vitest I knew I could finish features like this.

submitted 5 days ago • 4 comments

This is one of the biggest releases we ever did!

submitted 5 days ago • 1 comment

✋ [email protected] is out! - Browser Target Changed to Baseline Widely Available - Node 18 support dropped. Vite is now distributed as ESM only Plus fixes and deprecated feats removals, preparing for rolldown. Help us test the beta and report back 🙏 github.com/vitejs/vite/...

submitted 5 days ago • 2 comments

Today we are excited to announce Rolldown-Vite: a technical preview of the version of @vite.dev entirely powered by the Rust stack we built over the past year (Oxc + @rolldown.rs) voidzero.dev/posts/announ...

submitted 8 days ago • 3 comments

For the Oxlint 1.0 announcement, I'd like to show more real world performance numbers on large repos. If Oxlint has been satisfactory, would you be keen to send me the numbers Oxlint reports at the end? If you have never tried Oxlint but has a large repo: `npx oxlint@latest`.

submitted 8 days ago • 9 comments

Seriously, if you need help, get in touch.

submitted 9 days ago • 0 comments

After watching, make sure to check out @scottspence.dev blog post about this. bsky.app/profile/scot... He not only applied the patterns i showed in my talk but also expanded and improved on them, with feedback from @erus.dev too. A great testament of collaboration in our communities.

submitted 9 days ago • 2 comments

In today's released talk from Svelte Summit Spring 2025 @dominikg.dev talks extensively about testing your Svelte applications with Vitest and Playwright — Testing, 1 2 3 4. www.youtube.com/watch?v=ljmU...

submitted 9 days ago • 0 comments

Efforts to extend the Web as Temporal are just so incredible in scale. Grateful there are folks who are able to walk such lengths to make things better for all of us. This recording from Igalia Chats tells the story of how the feature got to Stage 3, four years ago (!): www.igalia.com/chats/Temporal

submitted 10 days ago • 0 comments

Trying to collect some data: what package that you know/maintain have transitioned to shipping ESM-only/ESM-first after it's unblocked by the support of require(esm)? Any tips/experiences to share?

submitted 10 days ago • 8 comments

I got involved with oxc because I just showed up, looked at the issues available and suggested solutions, and started making contributions. It was also nice to not have the pressure of being publicly assigned to it so I could take my time and learn as I went.

submitted 11 days ago • 1 comment

This! For bugs and small issues. The best thing about OSS is you can fix irksome bugs yourself and usually a great learning opportunity. However, for any big changes do raise an issue first to make sure the change is wanted in the project, and the planned approach is the best way.

submitted 11 days ago • 0 comments

If you find an OSS issue that calls your attention, go for it. You don't need to ask permission to start working or have it assigned to you. If someone else sends a PR before you, that's great. You can use your knowledge of the issue to help review the PR, add tests, and validate the approach.

submitted 11 days ago • 3 comments

@sli.dev now support 𝗰𝗼𝗱𝗲 𝗴𝗿𝗼𝘂𝗽 syntax and automatic title icon matching (like VitePress)! Thanks @antfu.me for inspiring me to implement this feature! See more details on: sli.dev/features/cod...

submitted 12 days ago • 1 comment

well thank you @syntax.fm - what a lovely episode to listen to ❤️

submitted 12 days ago • 1 comment