(This is part of an open ended series of posts where I write down random things I feel are sharable from the years of mailing lists I’ve not caught up on…)

My original plan for Laravel News was to go through all the 12.x ones week by week and apply them to my codebase as I upgrade it. But turns out that I already upgraded EiPS to 12 so that plan won’t work as stated. That also feels like the ‘breakable toy’ project I use for learning AI assisted development. (More on that in a month or so.)

Here is Part 1. These from Laravel 12 launch through July 2025.

  • I still havent fully wrapped my head around Blade Components yet, but looks like Dagger is something to remember for a year from now when I get to the edge of the envelope of them.
  • Cleaner Queue Chains with Laravel’s Enum Integration is the best use of Enums I’ve seen yet. Or it could just be I’ve spent the last decade routing messages to specific busses based on a tonne of different criteria.
  • flux is ‘The official Livewire component library’ which means I probably should have bought it already. Need some paying customers first. My cobbled together ones are fine until then.
  • Catch Unintended HTTP Requests in Laravel Tests – January has a lot of high-level themes, but one of them is paying down my test debt. This is 100% going to be used. (I still kinda hate that Cashier hits the test APIs…)
  • I have no use for Pinout but it is super cool. I do have a couple Raspberry Pi’s in storage though…
  • World feels like another package I have hand-crafted a couple times.
  • I do need to really grok fluent() fpr requessts and responses
  • I swear. A lot. EiPS likely shouldn’t have my habits in it, so something like squeaky needs an evaluation. It already uses banbuilder so maybe a bake-off is in order.
  • Disposable Email Detection in Laravel feels like it should just be a default rule for most apps.
  • Backpack – At some point I’m going to need to build a dashboard for EiPS. Or maybe I just buy one.
  • Using Database Comments to Track Columns With Sensitive Data is super clever. According to Google comments do not count towards the otherall table size limit. But constantly referencing metadata might have implications. But this could be quite the compliance hack. Heck, you could extend this to encrypt those columns, etc.