This article covers new changes and improvements to Spike ranging from v1.6 to v2.1 (latest).

If you're not sure what Spike is or what it does, be sure to checkout the main page or the documentation.

Full Livewire 3 support

Spike v2 now runs on Livewire 3, which means you can now upgrade your Laravel app to Livewire 3 as well!

To learn more about Livewire 3, go to the new Livewire website. To upgrade your Laravel app from Livewire 2 to Livewire 3, you can visit the Livewire Upgrade Guide.

Installing Spike for Teams

Previously, in order to set up Spike for teams (when using Laravel Jetstream), you would have to publish and modify a few migrations. While not too much work, it can still be inconvenient and prone to mistakes.

Now, when running spike:install for the first time, you can pass a --teams flag which will set up Spike so that the Team is the main billable. This works great if you want your subscriptions and credits to be scoped on a team, rather than each individual user.

php artisan spike:install --teams

This option is also documented on the Spike's Getting Started page.

Bug fixes and performance improvements

First and foremost, the latest versions include several bug fixes which improve how Spike behaves in various edge-case scenarios. Here's a few examples:

  • Improved the performance of fetching credit balance
  • Fixed the bug where only one subscription without payment was allowed

Always remember to keep Spike up to date for latest improvements and bug fixes.

How to upgrade?

Simply run the Composer require command with the latest version.

composer require opcodes/spike:^2.1

If you're installing Spike from scratch, learn how to Install Spike here.

If you have questions, issues or feature requests for Spike, don't hesitate to reach out to me on arunas@arunas.dev .