AdonisJS - A fully featured web framework for Node.js
AdonisJS is a TypeScript-first web framework for building web apps and API servers. It comes with support for testing, modern tooling, an ecosystem of official packages, and more.
adonisjs/core: 🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence
🚀 The Node.js Framework highly focused on developer ergonomics, stability and confidence - GitHub - adonisjs/core: 🚀 The Node.js Framework highly focused on developer ergonomics, stability and conf...
antfu/shikiji: A syntax highlighter based on TextMate grammars. ESM rewrite of shiki, with more features and capabilities.
A syntax highlighter based on TextMate grammars. ESM rewrite of shiki, with more features and capabilities. - GitHub - antfu/shikiji: A syntax highlighter based on TextMate grammars. ESM rewrite of...
Rails 7.1 adds support for MessagePack as a Message Serializer | Shakacode
Rails 7.1 welcomes MessagePack, a binary data format delivering significant payload size reduction and performance improvements over traditional serializers like JSON.
Update: Judging by this commit and the current status of main, this should be fixed for Rails 8. Great PR thread about this, by the way. In the history of Ruby on Rails, one of the healthiest pressures to keep memory usage down has been the special role Heroku has played as "easiest place to get started hosting Rails apps". In general, Rails Core and Heroku's staff have done a pretty good job of balancing the eternal tension between advancing the framework while still making sure a new app can comfortably run on Heroku's free (or now, cheap) "dyno" servers over the last 17(!) years. Being able to git push an app to a server and have everything "just work" has always been a major driver of Rails' adoption, and it's seen as obviously important to everyone involved that such a low-friction deployment experience—even if developers ultimately move their app elsewhere—is worth preserving. And that means being cognizant of resource consumption at every level in the stack. Anyway, there have been numerous bumps in the road along the way, and I think I just hit one. I just pushed what basically amounts to a vanilla Rails 7.1.3 app to Heroku and immediately saw this familiar error everywhere in my logs: Error R14 (Memory quota exceeded) It started literally minutes after deploying the app. The app was taking up about 520MB. What gives? I even remembered to avoid loading Rails' most memory-hungry component, Active Mailbox!
Set a new default for the Puma thread count · Issue #50450 · rails/rails
We currently set the default Puma thread count to 5. That's very high. It assumes you will massively benefit from a bunch of inline 3rd party calls or super slow DB queries. It's not a good...
Announcing RBS support for AWS SDK for Ruby V3 | AWS Developer Tools Blog
RBS is a language to describe the structure of Ruby programs. We are happy to announce that AWS SDK for Ruby V3 now supports RBS type signatures! RBS support is released in aws-sdk-core version 3.191.0 and in every service gem (such as aws-sdk-s3) that depends on this version of core. RBS signatures are currently code […]
In September, 2020, our team at Shopify released a Ruby gem named Packwerk, a tool to enforce boundaries and modularize Rails applications. Since its release, Packwerk has taken on a life of its own, inspiring blog posts, conference talks, and even an entire gem ecosystem. Its popularity is an indication that Packwerk clearly filled a void in the Rails community.