I had a good time at Vue.js Amsterdam! I happened to be sitting next to a newsletter subscriber, greetings go out to Julian!
We're close to 3000 subscribers of this newsletter which is a big milestone for me. It would help me a lot if you would recommend the newsletter to your colleagues and friends. 🙏🏻
🔥 Nuxt Tip: How Nuxt Uses Nitro, h3 and ofetch Internally
If you are using Nuxt 3 you might stumble upon one of the following tools: NitroNitro, h3h3 or ofetchofetch. I often see that people are confused by these tools, so let me clarify their responsibility and how Nuxt uses them internally.
All of the following packages are published in the UnJS ecosystem which consists of 56+ packages.
ofetch
Nuxt provides access to ofetchofetch via the $fetch$fetch API. Its described as "A better fetch API. Works on node, browser, and workers".
It can smartly parse JSON responses (with access to raw response if needed) and request body and params are automatically handled, with correct Content-TypeContent-Type headers.
h3
h3h3 is an H(TTP) server framework built for high performance and portability running in any JavaScript runtime.
Its event handlers automatically convert responses. For example, if you return a JSON object it will be stringified and sent with the default application/json Content-Type header. If an event handler returns a Promise, h3 will wait for it before it sends the response. Additionally, it provides a set of useful helper functions for body parsing, cookie handling, redirects, headers and more.
Nitro
NitroNitro uses h3h3 internally and is a server toolkit to create web servers with everything you need and deploy them wherever you prefer.
It provides cross-platform support for Node.js, Browsers, service-workers and more. Additionally, it supports API routes and middleware and a development server with hot module reloading
Sunday, January 5, 2025 Update: Bluesky images work again and thus the Great Art on Bluesky channel is back. If you're on Bluesky please subscribe. # The crazy thing about Bluesky's API is they took already standardized things like links and enclosures, and after 20+ years came up with new definitions. Makes our apps more expensive to maintain, and we waste time and human wear and tear on stupid bullshit make-work. Developers are people, and our work is already horribly overly complex, we're working at the edge of comprehension, and what the fukc let's throw some more unnecessary complication into the mix. Arrogance, narcissism, whatever the source is, it's not a good way to introduce yourself. And, even better, after you go through the maze they break it, with an error message about legacy blob bullshit. They've already done this, and they're just getting started. It's why I say they should just adapt to RSS instead of trying to forc...
评论
发表评论