1/1 End of last year @redwoodjs removed their funding of their graphql framewor, put it im maintenance ans create a new one. It felt like a redwood tree fell on our foot. Redfoot, we decide, will be the untangled underlying fastify framework. It took us half a year, but we managed it. Redwood was a great help, but we wont look back. The new framework gives us some advantages:
#fastify
0 posts0 participants0 posts today
The Story of Fastify and Vue, by @anothergalvez.bsky.social:
hire.jonasgalvez.com.brThe Story of Fastify + Vue
React Server Confusion, by @anothergalvez.bsky.social:
https://hire.jonasgalvez.com.br/2025/apr/8/react-server-confusion/
hire.jonasgalvez.com.brReact Server Confusion
If you're a developer, #SurrealDB might be the ultimate prototyping tool for your data. Check out my latest blog post on using SurrealDB with Node.js and Fastify! #sql #nosql #nodejs #fastify https://reverentgeek.com/meet-surrealdb-nodejs/
ReverentGeekMeet SurrealDB: The Multi-Tool Database Your Node.js App Needs – ReverentGeekDo you have a need for relational and non-relational data in the same app? You should check out SurrealDB! Here's how to build a basic CRUD API using Node.js and Fastify.
Hi!
I'm Adrian, a FullStack #Developer looking for a job either in #Québec (or from it if you allow for remote work). I already have a permanent and open visa
I have experience building and maintaining web apps and APIs, designing systems, doing #DevOps and a bit of #BigData, #MachineLearning and #IoT
I'm experienced using #Elixir, #Phoenix, #LiveView, #NodeJS, #TypeScript, #Fastify, #Express and #Python ; and on the DevOps side in CI/CD pipelines (either #GithubActions and Gitlab CI/CD), #Docker and a bit of #Kubernetes
I was tasked with a lot of the #innovation happening in my previous company, researching tools, librairies, patterns or general technologies either for our own #DeveloperExperience or for our products
I also wrote a lot of technical and non technical documentation and internal presentations, and even participated in a few meetups. You can read some of my writing on my blog: https://blog.adrianc.eu
You might also have seen me on a few Elixir-related Discord servers, or even Bluesky (@adrianc.eu) and Twitter ; either sharing tech news, helping people, reading in book clubs or just chatting
I’m open to full-time right now, contracting work can be discussed.
I'm looking for any developer position, not only #ElixirLang, even though it represents most of my experience. And if the technology you're using isn't on my resume, give me a chance! I'm a fast learner and I might anyway have studied it in class :P
DM me for more info, like github link, my resume or anything :)
Boosts, responses and DM welcome, of course!
#MyElixirStatus #FediJobs #FediJob #FediGetHired #OpenToWork
EDIT: I already have a visa, it was not super clear before 
AdrianCAdrianCCuriosity propelled
An SSR Performance Showdown
Comprehensive #SSR Performance Testing:
• Test setup: 2398 div elements spiral rendering on #NodeJS v22, #M1Mac with 8GB RAM
Performance Rankings (requests/second):
• #fastifyhtml: 1088 (baseline templating)
• #Vue: 1028 (best full-featured performance)
• #Svelte5: 968 (pre-release version)
• #SolidJS: 907 (impacted by hydration IDs)
• #Preact: 717 (lightweight alternative)
• #React19: 572 (RC version)
Testing Environment:
• Built using #Fastify and @fastify/vite
• Production builds tested
• Consistent styling and template implementations
• No client-side reactivity features
Key Findings:
• #Vue and #Svelte offer best balance of performance and ecosystem maturity
• Hydration markers impact performance (demonstrated in #SolidJS)
• Simple templating (#fastifyhtml) outperforms full frameworks
Source: https://blog.platformatic.dev/ssr-performance-showdown
Platformatic Blog · An SSR Performance Showdown
My PR supporting #graphql_tag style queries got merged and released in #mercurius 5.0.0!
This enables easier handling of fragments in #graphql, and I decided to follow up with a real world example in the PR post release to aid as a future reference for people: https://github.com/mercurius-js/mercurius/pull/1108#issuecomment-2362986609
Thanks for the merge @mcollina 
GitHubfeat: support pre-parsed queries (eg. `graphql-tag`) by voxpelli · Pull Request #1108 · mercurius-js/mercurius
If you're seeing Dependabot PRs on Node projects named "Bump find-my-way and fastify" today and were not already on Fastify v5, be aware you'll need to update your Fastify config/usage (see https://fastify.dev/docs/latest/Guides/Migration-Guide-V5).
The `find-my-way` (indirect for me) update requires Fastify v5 apparently and that broke several projects which weren't on Fastify v5 yet. Luckily (well, intentionally, obv) the breakages were caught by CICD in dev.
fastify.devV5 Migration Guide | FastifyThis guide is intended to help with migration from Fastify v4 to v5.
Continued thread
Updating the Fastify logger constructor config has allowed the web server to start now. I'm using a parent logger so this meant adding:
`loggerInstance: parentLogger` to the Fastify instantiation, e.g. the last property in:
```
const fastify = Fastify({
trustProxy: true,
keepAliveTimeout: 3600000,
loggerInstance: parentLogger
});
```
Tests now pass locally, 
for the same on Cloud Build!
Docs:
https://fastify.dev/docs/latest/Guides/Migration-Guide-V5/#new-logger-constructor-signature
fastify.devV5 Migration Guide | FastifyThis guide is intended to help with migration from Fastify v4 to v5.
Dependabot raised a PR against on of my Node projects this morning and the build failed. The PR was to move to Fastify 5 (from 4.x).
I pulled the branch down and sure enough the web server no longer starts. I'd spotted Fastify 5 now requires Node 20+ but I'm already on that.
Time to dig in to the migration guide: https://fastify.dev/docs/latest/Guides/Migration-Guide-V5/
#Fastify #Node
fastify.devV5 Migration Guide | FastifyThis guide is intended to help with migration from Fastify v4 to v5.
Replied in thread
FYI – I’m available for #coaching / #teaching / conference talks / shorter #freelancing gigs (1-2 days at a time)
I’m right now primarily focusing on my own projects but happy to share my experience with others + never wrong to refill the wallet a bit.
Topics I’m extra thrilled about: #TypesInJS #vanillaJS #nodejs #fastify #opensource #npm #eslint #linting #maintainership #restAPI
[1/2]
I think I've found my #SPA #SSG #SSR holy grail:
- #Preact with no build step (#ESM only)
- HTM for JSX-like syntax
- preact-render-to-string for server-side rendering
- preact-router for all routing
- Preact's `hydrate` method
On the server (I use #koa, but works with #Fastify or #Express, too) routes can either serve
- Pre-rendered static markup
- Pre-rendered app routes that get hydrated on the client (optionally switching to client-side rendering)
- Fully client-side rendered apps
Replied in thread
@mcollina #npmRelease #fastify (adding hashtags makes it easier to follow, and so far I'm the only one using #npmRelease, would be nice to get some traction for such a one as I would love to find releases from people I don't yet follow here. That and #newNpmModule for any new modules)
Deploying a Fastify & Vue 3 Static Site to Heroku
A small write-up on how to deploy a Vue 3 static site to Heroku with a Fastify Node.js backend server to serve the static files. By the end, you’ll have a clear understanding of the process and be able to deploy your own static site with ease: https://www.lirantal.com/blog/deploying-a-fastify-vue-3-static-site-to-heroku
Replied in thread
Alternatives to #Express:
Koa, which can either replace or complement both Express and Connect.
Fastify, which looks straightforward and very similar to Express. Plugin for templating (supporting Handlebars, Mustache, Pug and EJS): @fastify/view.
NestJS, which seems too convoluted and probably redundant since it works on top of either Express or Fastify (?).
Meteor: more of a platform. No tutorial for vanilla JS (only for React, Vue, etc), and not oriented towards SSR.
I’ll probably go for #Koa or #Fastify.
#JS #JavaScript 
#Node.js #Node
koajs.comKoa - next generation web framework for node.js
I quietly added #gitea as a service to https://coolify.io today with lots of bug fixes.
Currently working on adding #docker registry support to use private Docker images or any Docker registry!
CoolifyCoolifyAn open-source & self-hostable Heroku / Netlify / Vercel alternative.