Blog

Laravel's toArray collection method might not return what you might expect.

Need to handle image uploads in your Laravel app? In this post, we start with the basics and level up step-by-step—from a simple form upload to full-blown image handling with resizing, optimization, and a slick drag & drop UI. Whether you're building something quick or scaling up, there’s a Spatie package (or two) that can help you out.

Passkeys are very convenient for users to log in: they don’t have to type in an email/password, you aren’t redirected to a third party for authentication, and it’s fast.

We've made a new package that makes it easy to let your users authenticate to your app with passkeys.

Today we're launching php-operators.com, a little web page to browse, search, and learn more about all operators in PHP. Sure, you could just ask AI to explain them the you, but where's the fun in that?

We've been building Laravel applications with Livewire and Inertia for over 5 years. If you held an individual Spatie employee at gunpoint (please don't) and forced them to pick a favorite, you'll get a 50/50 split. It's like choosing between chocolate or vanilla ice cream: there's no objective winner (except vanilla). But when we look at the choice at hand as a team, it becomes easier to determine the right fit.

This latest update provides more flexibility for validating media uploads directly in Livewire or controllers, streamlining the process.

We just tagged & released a new major version of spatie/laravel-csp, a package to manage your Laravel app's content security policy. The development goal for version 3 was to reduce the boilerplate of configuring a policy for common services like Google Tag Manager, Fathom Analytics, Adobe Fonts… In addition, we've made it easier to add your own directives through your configuration file, without writing additional code.

In 2023, DHH's decision to remove TypeScript from Hotwire and Turbo caused some drama in the JavaScript community. At Spatie we’re open source maintainers too, so this sparked an interesting debate: What can users expect from our open source packages?

Today, we're reintroducing Laravel Backup Server with a fresh version 4 release. It comes with refactored internals and more control over notifications, but most importantly: we're removing it from our shop and open sourcing it instead.

With Mailcoach, we handle email lists with up to millions of subscribers. Keeping queries, and especially search queries fast is paramount for a good user experience.

A large, legacy codebase can't be overhauled in one take. An undertaking of that magnitude is risky and can hinder progress on features users are waiting for now. On the other hand, we want to avoid a never-ending race by coupling new features to legacy components. Configuring import aliases can make the distinction of "legacy, to be removed" or not explicit.