In the next version of ArkType, any Standard Schema is a valid definition.
Zod migration is about to get a whole lot easier🚀
01.12.2025 18:39
👍 38
🔁 5
💬 3
📌 0
In the next version of ArkType, any Standard Schema is a valid definition.
Zod migration is about to get a whole lot easier🚀
To be fair, the old version is linking to an now-archived project from 2024 :D
I guess it shouldn't be too hard to get the correct github repo listed again ☺️ Good luck with that!
No worries! :) I guess the operator was considered staled by someone at Kubernetes, which the changelog in the footer may suggest: github.com/kubernetes/w...
> We provide our own Kubernetes Operator at ngrok, -->and are listed as a recommended ingress controller on the Kubernetes website<--.
What am I missing?
I've checked the link and could only find three links to the actual nginx website. The only mention of ngrok was the changelog at the bottom.
I do get the argument about having an entire module configured/modified/annotated using directives. However, I do think that configuring each export is still superior and more explicit. Again, you might want to configure them differently, which means you don't have to split them in different files.
Not all frameworks use magic functions. Now, does that change your standpoint or do you still argue that a random string is better than an explicit function call, which would provide a lot more flexibility and actually less magic?
Let me know if you need further testing. Happy to help! :)
Since I've never been on that website before: Very, very beautiful website! I really do love the attention to detail in those animations with all of the unique ideas.
Outstanding work! Really looking forward to the cursor size feature :) Great idea and obviously great for accessibility!
Reloading the website in between changing the cursor size didn't work either. It looked the same all the way.
Initially, I also thought the cursor looked a lot bigger when visiting the page with the default cursor size, but that may be intentional.
I've quickly tested it using the latest version of Windows 11 using Microsoft Edge 141.0.3537.99:
In both cases, the default cursor size (smallest) and largest, the cursor on the website *did not* scale up or down.
Meeeeeeeeeeega! Von solchen News wollen wir mehr hören 😍
🚀 Announcing TanStack.com Start v1 Release Candidate!
Upgrades ↓
✨ Unified Route Tree: no more server-specific files
🔐 Type-safe middleware & server context upgrades
🛡 CSP/nonce support
⚡ Now works with any native Vite Env plugin
🌀 Zero-JS: any server handler can render!
✨ I just published a brand-new blog post about a modern CSS feature!
But, honestly, I’m still on the fence about it. 😅
In this post, I’ll dig into the gnarly issue I ran into, and share three possible workarounds. Along the way, you’ll learn a bunch about the CSS cascade and specificity!
FYI: In your "Select In Form" case, as soon as you select an option, the formatted item label will display "UNKNOWN" instead of the option's label. However, submitting the form will indeed render the correctly selected option!
All the other cases do seem to work just fine :)
On October 15th 2025, Cloudflare is enabling Web Analytics for all free domains by default—helping you see how your site performs around the world in real time, without ever collecting personal data. https://cfl.re/3IuBjuT
Screenshot of Safari 26 in "tabs at the top" mode showing a webpage that is set to `viewport-fit=cover` and the dynamic toolbars scrolled away (minimized). The viewport is too short and the safe area insets are all wrong. Device: iPhone 13 Pro.
Screenshot of Safari 26 in "tabs at the top" mode showing a webpage with the dynamic toolbars scrolled away (minimized). The viewport (blue box) is way too short and does not toch the very top of the screen. Device: iPhone 13 Pro.
Viewport behavior in Safari 26 is utterly broken. 🙄😭
Time to get Viewports into #Interop2026 because viewports on iOS have gotten only worse since I did the initial research in, *checks notes*, 2022 — github.com/web-platform...
{npm i, {pnpm,yarn,bun} add} nuqs@latest
📦 nuqs@2.6.0 is out! 🚀
- ✨ `processUrlSearchParams` middleware: sort the querystring alphabetically (for SEO & cache) or process it before updating the URL.
- 💎 Zod codecs community parser
- ⚠️ Log a warning when using debounce with shallow: true with a link to docs
Try it out: pnpm add nuqs@latest
🛠️ New Article: The Basics of Anchor Positioning
I wrote an article covering some basics of CSS anchor positioning. Really excited to share this one! 🤩
🔗 ishadeed.com/article/anch...
#CSS text-box
a very exciting feature!
available in:
Chrome 133 & Safari 18.2
My post on Chrome Developers:
developer.chrome.com/blog/css-tex...
↪ nerdy.dev/text-box-trim
The big underlying question is always: *Should* my change be fully reflected to the outside („public”), or is my change supposed to be „internal only”?
That may or may not be related to me growing up learning C# before slowly dipping PHP, which just got types with v5, and then JS, followed by TS.
If one of those functions will cause an error because I've changed some internal data structure, then it's up to me to figure out how to handle it in *this* particular case, giving me more control.
To me, this is more valuable and more useful in larger code bases.
Depending on your TypeScript configuration, and obviously on your code base, a change in your data structure might cause an error elsewhere, where it's not supposed to error.
I like having explicit return types so that I can control how much will actually flow out to external code.
I know there are tons of arguments about that it's more convenient to have the return type being implicit. I'd argue the opposite. Think about twice when you make a change somewhere and it changes the return type of something that you're not really thinking about at the moment. This will catch bugs.
Yes, to avoid accidental changes to the return type. This is especially important for library code.
It is also super useful when trying to help the compiler for figuring out module boundaries without having to analyze anything but the return type.
TypeScript 5.9 Beta just went out! Try it in your project and let us know what you think:
devblogs.microsoft.com/typescript/a...
Alarmstufe Eis, wir haben einen Notstand. Alle Frauen und Männer an die Eistheken. Erbitte um sofortiges flächendeckendes Spaghetti-Eis-Feuer auf der linken Flanke, wir drohen dort einzubrechen!
Why does Florida now look like a bull‘s testicles?
⚡️ Vite 7.0 is out!
- Browser Target Changed to Baseline Widely Available
- Node 18 support dropped. Vite is now distributed as ESM only
- And feats, fixes, and cleanups, while we prepare for rolldown!
Europe is not a country. It's not that hard.
