Blog

Read about new features, upcoming updates, and useful tips for using Ray.

Making electron's IPC typesafe end-to-end

Image of Dries Heyninck

Dries Heyninck

Quick tips: Sending Laravel output to Ray automatically

If you're using Laravel and the Laravel integration for Ray, you can configure it to send many different events, queries, requests and other calls automatically from your project to Ray.

Image of Jimi

Jimi

Introducing Ray 3.0

After months of beta releases and getting great feedback from our testers (seriously, thank you!), we're launching Ray 3.0 today.

Image of Jimi

Jimi

Ray 3.0 Beta is here!

It’s been a bit quiet from us these last few weeks, but for good reason. We wanted to hand you a beta we’re genuinely proud of. Our full rebuild of Ray has almost hit 100% feature parity with Ray v2 — just… better, everywhere.

Image of Dries Heyninck

Dries Heyninck

Sign of life

It's been a while since our last blog post. But we're back! Bringing you bi-weekly updates on our progress building the third iteration of Ray.

Image of Dries Heyninck

Dries Heyninck

Mixing up our styling recipe for Ray v3

When it comes to styling, Tailwind is almost always our go-to choice, and Ray is no exception. Its utility-first approach provides a solid foundation. But while Tailwind provides a solid foundation, it doesn’t directly answer questions like: How do we handle component variants? How do we override styles cleanly? Or how do we compose styles in a way that remains scalable?

Image of Sébastien

Sébastien

IPC in Electron

In Ray 3.0, we updated how the renderer and main processes communicate within our Electron app. While we’re still using the familiar React and Electron stack, we switched to a more dynamic, event-driven approach for IPC. This change simplifies communication, better integrates with React’s lifecycle, and adds security by whitelisting events. By drawing from existing community solutions, we’ve made our IPC system more efficient and easier to maintain.

Image of Sébastien

Sébastien

Using Ray with your Pest tests

Learn how to use Ray and Pest together to streamline debugging in Laravel, including opening separate Ray windows for tests and automatically checking for stray Ray calls before production. Plus, explore Pest’s architecture tests and a handy Ray inspection method for quick value checks.

Image of Tim

Tim

Debug without breaking your flow

Ray keeps all your debug output neatly organized in a dedicated desktop app.

Licenses are valid for 1 year and managed through Spatie. Licenses purchased before Ray 3 remain valid. VAT is calculated at checkout.