Ray 3.0 is coming soon — rebuilt from the ground up to be faster and more powerful. Download the beta

The Ray blog

Shining a light on internals and updates.

Sniffing out stray ray() calls with Pest architecture testing

Whether you're building a shiny new feature or refactoring a bug deep in a legacy codebase, before you merge your work to production you want to get rid of all those ray() calls you littered the codebase with. You'll probably get rid of most of them on time, but every now and then a stray call gets forgotten during code review.

Sebastian

Automatically starting Ray on MacOS

Using a bit of AppleScript, you can automatically start the Ray desktop app from your PHP code.

Freek

Find where a method was called in PHP

Methods that get called in a bunch of different places can be tricky to debug. Find out where your methods are called with debug_backtrace().

Sebastian

Detecting N+1 issues in your Laravel project with Ray

Learn how to detect and resolve N+1 issues in your Laravel project by using Ray.

Tim

Debugging Livewire components using Ray

Ray has a few tricks up its sleeve to make debugging Livewire components very easy. Let's take a look!

Freek

Ray as a debugging companion in busy integration tests

Ray is a great companion when debugging a test. However, in busy integration tests it can be hard to find out which logs matter and which don’t.

Sebastian

Expanding objects and array using Ray

We've added a new method that makes it easier to inspect the content of objects and arrays.

Sam

Freek

Copy output from Ray to your clipboard

At Spatie, we keep working on Ray continuously. We’re adding small quality-of-life improvements every week. We’re happy to announce that you can now copy logged arrays and objects to your clipboard from Ray.

Tim

Use Ray to find queries that are slowing you down in your Laravel project

Database queries are often one of the main bottlenecks when it comes down to your app’s speed. Not only is it important to give your users a snappy experience of your app, slow queries can cause major problems when your app is experiencing high load. Luckily Ray makes it super easy to find out what queries you should optimize.

Tim

Ray is the best home for Next.js debugging output

Next.js development comes with a unique challenge when it comes to debug logging. With different rendering options and environments, I've found myself switching between the node.js developer console and the browser console too many times.

Sam

Use ray()->trace() to figure out where a call came from

Easeliy find your way in codepaths by printing backtraces with with ray()->trace()

Tim

Testing mails in Laravel using Ray

One of the most valuable features of Ray is its ability to preview emails in your local environment. This feature will also help you test entire mail flows.

Freek

Inspecting the return value of a function using Ray

Using the pass function, you can easily debug return value.

Freek

Easily inspect the contents of a Laravel collection

We automatically register a ray() collection macro that allows you to look inside the collection at any point in a chain.

Freek

Automatically clear Ray when running tests via PHPUnit or Pest

Learn how to automatically clear Ray's screen when running a test.

Freek

Understand and fix bugs faster

Ray is a desktop application that serves as the dedicated home for debugging output. Send, format and filter debug information from both local projects and remote servers.

Or learn more…