Blog

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.