Embarrassing, don’t you think?
Strong type inference was the major USP (iirc) when Zod first came out, and is shown literally on the first page of the usage docs.
This. We never worried so far about these supply chain attacks because we only update deps when there is a reason to, ie security alerts that actually can affect us (dependabot noise on dev deps is not helping) or significant improvements it is demonstrated we will benefit from
Fork your dependencies, trim them to only your use case, never update unless it breaks for your users. I’ve been vocal about this for 10+ years. I’ve always said that updating is way riskier than latent bugs (which can be tracked and CVEs monitored).
If you are updating a dependency, it’s on you to analyze every single commit in the full transitive set of dependencies. If you dont see anything compelling, dont update!
I remember at HashiCorp once in awhile an engineer would try to update a dep or replace a DIY lib with an external one and id always ask “show me the commit we need.” Dont update for the sake of it.
Feeling pretty swell about this mentality with all the supply chain attacks happening.
HEADS UP. Popular JSON formatter extension has started injecting geolocation tracking and donation UI into websites
Reddit thread seems to think they are also swapping tracking IDs for affiliates (a-la honey)
Uninstall and switch to another one
this week, i bumped into a thread debating whether the days of Figma are over. this made me reflect hard about the ultimate role of design software, so i blogged about it:
https://t.co/TAvtmBUc2a
If Bill Gates was alive, he would be proud to see Rust finally being integrated into the Linux Kernel.
Imagine seeing the project you created getting this far.
🎉 And we're live! 🎉
We just launched CSS Wrapped 2025: our annual recap of all things CSS & web UI that landed in Chrome over the course of the year. 🚀
This is a big one! We highlighted 22 new features to help you build better on the web.
Check out: https://t.co/bdqB5Y4smN
So far it looks like i will build yet another OAS plugin or router myself, not very happy with the state of the art in the modern JS space. Will document the journey of course.
👋 I am evaluating options to build an OAS 3.1 (or 3.2) server in TS. It should to be JS runtime agnostic, use standard-schema description and validation, with strong static typing in the handler. I have studied Hono and Elysia default plugins. Is there anything else? RP pls😘