We love reading, watching, and listening in order to constantly update our skills and learn new perspectives. Here are some of the exciting pieces we learned from this month.
Which of these August 2022 picks still hold up?#
All eight picks, and the SVGBackgrounds site in the Visiwig item, are still online, and most still earn a look in 2026. Turbo, Zustand, Minitest, RSpec and Patterns.dev all have newer releases or new material. grex-js has not shipped a version since August 2023, though the Rust grex tool it wraps has. HypeScript was always a learning project. Visiwig and SVGBackgrounds offer both free and paid graphics.
The table gives each pick's status as of November 11, 2026.
| Pick | Where it stands in November 2026 | Still worth a look? |
|---|---|---|
| Turbo | Turbo 8.0.23 shipped January 29, 2026, the same day as the turbo-rails gem 2.0.23. | Yes. Frames and streams are still core chapters of the handbook, now joined by morphing. |
| Zustand | Version 5.1.0 shipped November 6, 2026. It needs React 18 or later. | Yes, for apps on React 18 or newer. |
| grex-js | The npm package is still 1.0.2 from August 2, 2023, which matches Rust grex 1.4.2. The Rust command line tool reached 1.4.6 on November 14, 2025. | Yes, but the Rust tool is the newer one. |
| Minitest vs. RSpec article | Written July 28, 2022. Since then, Minitest reached 6.1.0 and rspec-rails reached 8.1.0, both on November 6, 2026. | Yes, read with the update below. |
| Visiwig | Free and premium graphics, plus a shop. | Yes. |
| SVGBackgrounds | Free graphics with attribution. As of November 2026, the Professional plan costs $10 a month billed yearly, or $15 month to month, and drops the attribution rule. | Yes. |
| HypeScript | The README says it is meant only for fun and learning. The npm package needs TypeScript 4.7 or later. | For learning only. |
| AppSignal memory leak series | Two parts, published July 27 and August 10, 2022. Both parts still online as of November 11, 2026. | Yes. |
| Patterns.dev | Still free to read online, with an eBook or PDF download. It now covers Vue as well as JavaScript and React. | Yes. |
Three of these changed enough to need more than a table row: Turbo, Zustand, and the Minitest and RSpec pair.
Digging Into Turbo with Ruby on Rails 7#
This article provides a nice intro to Turbo. The author goes over the high points of frames and streams, and gets you up and running quickly with a simple To Do app.
What changed in Turbo since the Rails 7 intro?#
Turbo 8.0.0, released February 7, 2024, added page refreshes with morphing, View Transition API support for navigations, and prefetching a link's page when the user hovers over it. It also removed TypeScript from Turbo's own codebase. Frames and streams, the two ideas the linked article teaches, are still core Turbo, and the Rails guide still covers their helpers.
A page refresh normally replaces the whole page body. With morphing on, Turbo updates only the elements that changed and leaves the rest alone. The common case is a form that submits and redirects back to the same page. Morphing is opt in, and you turn it on with a meta tag in the page's head. A second tag keeps the scroll position:
<meta name="turbo-refresh-method" content="morph">
<meta name="turbo-refresh-scroll" content="preserve">The page refreshes chapter of the Turbo handbook lists the values. The method is morph or replace, and replace is the default. The scroll setting is preserve or reset, and reset is the default. To keep one element out of morphing, such as a popover that should stay open, mark it with data-turbo-permanent. A frame marked refresh="morph" reloads with morphing when the page refreshes.
Rails apps also get a simpler way to push updates. A model that calls broadcasts_refreshes sends a refresh signal, and a view subscribes with turbo_stream_from. Each subscribed page then refreshes, and with morphing on, only the changed parts are redrawn. The Rails guide on JavaScript still covers the frame and stream helpers, such as turbo_frame_tag, through the turbo-rails gem. The handbook also has a chapter on going native on iOS and Android. Gnar's post Hotwire Native: Building Bridges shows one piece of that, a bridge component that turns a web button into a native one.
Zustand#
In a Javascript project, we're always looking for elegant ways to manage state. Zustand looks like one that we'll be checking out next time we need to start a project. It's small and looks like it will fit in nicely with how we like to develop applications.
Is Zustand still a good pick in 2026?#
Yes, Zustand is still a good pick for React apps on React 18 or later. This post listed it because "It's small and looks like it will fit in nicely with how we like to develop applications." It is still small, as this post said, and version 5.1.0 shipped on November 6, 2026. Version 5.0.0 arrived on October 14, 2024. It raised the minimum versions and reorganized its entry points, so a 2022 example may need small edits.
The v5 migration guide has the full list of changes. One change that breaks 2022 code is that create no longer accepts a custom equality function. In v4, the guide's own example passes shallow as a second argument to the store hook, so one selector can pick several fields. In v5, you can wrap the selector in useShallow instead:
// v4
import { shallow } from 'zustand/shallow'
const { count, text } = useCountStore((s) => ({ count: s.count, text: s.text }), shallow)
// v5
import { useShallow } from 'zustand/shallow'
const { count, text } = useCountStore(useShallow((s) => ({ count: s.count, text: s.text })))This step matters even if you never used shallow. The guide warns that in v5, a selector that returns a new object or array on every call may cause an infinite loop. React then stops with a "Maximum update depth exceeded" error. useShallow keeps the old reference when the top-level values have not changed, which fixes it for selectors that return flat objects or arrays. To keep the v4 style instead, import createWithEqualityFn from zustand/traditional and install use-sync-external-store.
grex-js#
It's 3pm. You're out of coffee. You need to write a complicated regular expression for your Javascript project. 😱😱😱Fear not friend, grex-js is here for you! This sweet app will generate a regular expression just for you based on the test case(s) you provide.
Minitest vs. RSpec in Rails#
At The Gnar, the vast majority of the rails applications we build are tested with RSpec. However, it's a good practice to periodically evaluate what other tools are available, and besides, it's fun to play with new tools. This article includes a rundown of different testing strategies, an introduction to TDD/BDD, and provides a comprehensive comparison between Minitest and RSpec from configuration through execution. RSpec still has our 🧡.
Minitest vs RSpec in 2026: what changed since the linked comparison?#
Minitest 6.0, released December 17, 2025, moved mocks into a separate gem and added a built in bisect command for order dependent failures. Both frameworks are still maintained, and both shipped new versions on November 6, 2026: Minitest 6.1.0 and rspec-rails 8.1.0. The comparison linked above is from July 28, 2022.
| Question | Minitest | RSpec (rspec-rails) |
|---|---|---|
| Comes with Rails? | Yes. The Rails testing guide names Minitest:: | No. Add the rspec-rails gem. |
| Latest release | 6.1.0, November 6, 2026 | 8.1.0, November 6, 2026 |
| Rails versions | activesupport 8.1.4.1 and 8.0.5.2 accept minitest 5.1 or later, with no upper limit. | The README says 8.x supports Rails 8.1, 8.0 and 7.2, and 7.x supports Rails 7.x. |
| Mocks and stubs | Since 6.0, in the separate minitest-mock gem. | rspec-mocks comes in as a dependency of rspec-rails. |
| Find an order dependent failure | minitest --bisect, added in 6.0. | rspec --bisect |
The 2022 article says Minitest supports mocking. Since 6.0 that needs the minitest-mock gem, as the table shows. For the choice itself, a short rule covers most teams:
- Existing suite: keep the framework it already uses. Rewriting passing tests adds risk and gives users nothing new.
- New app, no team preference: either one works. Minitest ships with Rails, so it needs no extra gem unless your tests use
Minitest::Mockorstub, which on Minitest 6 need the minitest-mock gem. - New app, team already writes RSpec: add rspec-rails, and match its version line to your Rails version.
For a real RSpec stub problem worked through end to end, read Factories, RSpec stubs, database queries, and you. It shows why a stub on a factory user is lost when the code queries the same row again and gets a different object.
What breaks when you upgrade to Minitest 6?#
Minitest 6 moves mocks and stubs into a separate minitest-mock gem and changes spec expectations, nil in assert_equal, plugin loading, the N variable and the minimum Ruby version, among other changes in its 6.0 release notes. A bundle update can pull Minitest 6 into a Rails app unless its Rails version caps minitest below 6, because activesupport 8.1.4.1 and 8.0.5.2 ask only for minitest 5.1 or later. Until the list below is done, pin the last 5.x release:
# Gemfile
gem "minitest", "~> 5.27"- Mocks moved out. minitest/mock.rb was dropped from Minitest and now ships as the minitest-mock gem. If your tests use
Minitest::Mockorstub, addgem "minitest-mock". - Spec expectations left Object. A call like
value.must_equal 3no longer works. Write_(value).must_equal 3, or usevalue(...)orexpect(...). - No nil in assert_equal.
assert_equal nil, valueis no longer allowed. Useassert_nil value. Since 6.0.3,assert_same nil, valueis refused too. - Plugins load only when asked. Require each plugin in test_helper.rb, or use
Minitest.load. CallingMinitest.load_pluginsbrings back the old automatic loading. - The N variable is gone. Minitest no longer reads
Nfor the number of parallel tests. UseMT_CPUinstead. - Ruby 3.2 or later. Minitest 6 requires it. The Ruby downloads page already lists 3.2 as no longer maintained, so an app on a maintained Ruby clears this one.
- Rails 8.1.2 or later. On Rails 8.1, update to 8.1.2 or later first. Rails 8.1.1 ran zero tests with Minitest 6 in rails/rails issue 56618, and 8.1.2 fixed it. On any other Rails version, keep the pin below 6 until your suite runs green on Minitest 6 in a branch.
The release added tools as well. minitest --bisect comes from the minitest-bisect project. It reruns your tests with a fixed seed and narrows them to the smallest set that still fails. A new minitest command also runs tests and accepts line numbers. Once the list passes, raise the pin to the 6.x line.
VISIWIG: click + page graphics#
If you have a website but you're not at the stage where you'd like to hire your own graphic designer, there are a lot of tools and libraries that can help spice up your content with unique graphics and backgrounds. Visiwig provides tools for generating basic background patterns, as well as a set of high-quality icons. And they're free. The same creator also created https://www.svgbackgrounds.com, which provides even more free SVG patterns.
Visiwig also sells premium graphics and graphic sets in a shop, alongside its free ones.
HypeScript#
You've heard good things about Typescript. But Hypescript lets you write Typescript…inside of Typescript. It's a lightweight implementation of typescript available from within Typescript's own Type Checking System. It's Inception. Typeception. DDUUUUUUNNNNNN.
How to Track Down Memory Leaks in Ruby#
Memory leaks: hopefully you never run into this problem, but if when you do this article might come in handy! This is the first in a series of posts about managing memory leaks in Ruby. This post covers how memory is allocated in Ruby (including improvements in Ruby 3.1) as well as garbage collection. It includes an example that demonstrates how to create your very own memory leak, and how to use the GC (GarbageCollection) module to uncover memory leaks in Ruby code. TL;DR: use an Application Performance Monitoring (APM) tool in prod.
Patterns.dev#
There's a new (free!) book about design, rendering, and performance patterns for Javascript and React on the block. The best part: you don't even need to click the download button! The content is available in the browser, documentation-style and boasts a delightful UI.
Contributors#
Learn more about how The Gnar builds software.


