Latest post
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.
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.
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.
+32 3 292 56 79
Our office is closed now, email us instead