The Release Candidate for TypeScript 6.0 is now available!
Read up on what's coming up with 6.0 & 7.0, and try it out on your codebase today!
devblogs.microsoft.com/typescript/a...
I'm sure the Ministry of Accuracy will make sure to keep things in check.
Love this.
"When new technology emerges, people get excited and forget to go back to the classics. They chase what's shiny instead of what's proven."
www.aihero.dev/tracer-bullets
Yeah I like preview better, it's a little more accurate as well.
This is what .NET versioning does for example but it's usually to include servicing support, so there are Beta and RC releases too that have standard support:
dotnet.microsoft.com/en-us/platfo...
Community highlights ✨
- @webpro.nl shares Unbash: zero dep bash parser written in TS
- @chrisnicholas.dev explains decoders, a Zod alternative
- @voidzero.dev highlights What's New in ViteLand: February 2026
- @yoav.codes showcases Electrobun with WebGPU
- @kentcdodds.com announces new TS workshop
CSS shape() landed in Firefox 148. It's similar to path(), but allows the full expressiveness of CSS…
And Cody has a spreadsheet/PDF with all 50 states' analysis for health insurance:
www.measuretwicemoney.com/choosefi
This is a pretty incredible episode and resource/spreadsheet.
open.spotify.com/episode/54TF...
somehow i cant stop watching
That's true. For myself, that's too risky a bet. I'd rather have my ducks in a row to continue to give my users a good service than risk being fined because I was hoping the paper pushers would never get to me. All it takes is one fine to put you under. Flying under the radar works until it doesn't.
And this is on top of the Big Ball of Privacy Law Mud.
This is one reason why some people are happy to be on platforms. The risk is you're tying your fate to them, but also they take care of all this stuff.
Conveniently left out of the "Build a seven-figure solo business" hustle webinars.
Yeah it sucks. I want to be in compliance but they make it really hard for small indie developers. Don't even talk to me about the new age assurance laws. 😭
(and Stripe Tax is basically a joke. It's extra PLUS you still have to set up tax merchant accounts in multiple countries.)
An MoR takes care of all that for you.
Stripe will happily take your payments without telling you that you've likely exceeded sales tax thresholds simply by having a customer in Germany pay you. Caveat emptor, indeed.
Not directed at me but re: last point, you want to learn more about Merchants of Record (MoR) providers like Paddle. They take care of sales taxes for SaaS and digital products. Highly recommend instead of plain Stripe (which is not an MoR).
📢 Practical TypeScript: Foundations to Fluency is now live!
First two workshops are free, the whole bundle is $200. There's a 40% discount for one week only! Check out the home page to answer your burning questions like: "What? AI writes my code now..."
www.epicweb.dev/practical-ty...
✨ What's New in ViteLand: February 2026 Recap
◆ Oxfmt Beta: 100% Prettier conformance
◆ @vite.dev 8 includes devtools
◆ @vitest.dev 4.1 beta adds aroundEach/aroundAll hooks
◆ @rolldown.rs becomes 9.6% faster
◆ Oxlint now supports 59/61 ts-eslint rules
◆ NestJS migrates to Vitest
◆ and much more 👀
I feel this hard, as someone who tries giving nuanced advice 😭
open.substack.com/pub/jakubgra...
Praise be to Cloudflare Transform URL Rewrite rules!
developers.cloudflare.com/rules/transf...
Yep, that was the culprit. Jeez! @developers.google.com what gives!
Stripping `iss` before it hits origin fixes it. I can also force it to match the correct ISS value for validation, so it will continue to throw an error if it is a true mismatch (the intent of the parameter).
I haven't confirmed removing the param fixes it, it's just what I noticed that breaks both my local and prod versions. If removing it fixes the problem, that's pretty concerning. Google adopted an OPTIONAL RFC and didn't version the change on their authorization endpoint. WTF.
This is the OAuth spec for iss. It is for mitigating mix-up attacks. Google must have recently adopted it in the front channel redirects.
datatracker.ietf.org/doc/html/rfc...
The symptom shows up as a redirect_uri_mismatch so that's what I was searching around to see if anyone else has been bitten by this. Worked for 13+ years and now just breaks!
I discovered it last night. I'm thinking I can mitigate it with Cloudflare in production so that's what I'm trying this morning.
The problem is the library strips known OAuth message params from the URI but it doesn't recognize `iss` as a message part. Maybe it's newer in the spec.
I can't find anyone else running into this, but Google OAuth sign in flow broke this or last month. It was very recent anyway, my logs only go back 7 days. The authentication code flow now adds the issuer (iss) query param on the redirect and it breaks my OAuth library which doesn't expect it. 😭
☕ Something's brewing for @nodejs.org releases starting with 27.x. Official announcement coming soon!
👀 Sneak peek: github.com/nodejs/nodej...
It's fully featured too since I got email notifications after opening my ticket.
Just wild! This is the product I want for my app but it's not even a product, it's just what he built to ship things faster.
And he's got a docs section, which is probably powered by Notion but that's just a guess
