Skip to content

Releases: hotwired-laravel/turbo-laravel

1.0.0

22 Dec 02:47
3e4ddaf

Choose a tag to compare

The first 1.0 release is here!! 🎉🎉🎉

Changelog

  • CHANGED: The Laravel Echo setup was commented out by default as users will likely not have the backend WS part of it set up when doing a fresh install of the package. Having it not commented out was only going to generate errors in the DevTools. So instead, it's now mentioned in the documentation to uncomment the Laravel Echo when setting up that part. Thanks to Espen Kristensen for the idea on Twitter.
  • CHANGED: The route guessing code was simplified quite a bit. Thanks to @sleicester. #42
  • NEW: There are now three new Blade components: <x-turbo-frame>, <x-turbo-stream>, and <x-turbo-stream-from> which can simplify using the custom HTML Elements a bit and also potentially improve the autocompletion part for IDEs since some can detect Blade components defined in packages. By @tonysm #41

0.18.0

11 Nov 02:56
44e2874

Choose a tag to compare

Changelog

  • FIXED: the previous way to opt-out of auto-wiring the Turbo middleware should was previously using a Facade and now it's using a config key

0.17.0

11 Nov 02:54
6ff03eb

Choose a tag to compare

Changelog

  • CHANGED: When handling invalid form submissions we were previously flashing the errors and redirecting to the form page (based on the resource route naming convention). This had to change because Turbo expects only successful responses to redirect, while invalid responses should return a 422 status code with the form containing the invalid messages. #36 Thanks to @bakerkretzmar @taylorotwell @tobyzerner for the help there.
  • CHANGED: The TurboMiddleware is now automatically prepended to the web route group. If you were already using it, either move it to the top of the group stack or remove it entirely from your HTTP Kernel.

0.16.0

20 Oct 00:43
fe9ded6

Choose a tag to compare

Changelog

  • NEW: We can now build and combine multiple Turbo Stream responses in a single Response. This should be an alternative to using a custom Turbo Stream view. #39

0.15.1

01 Oct 00:05
9086262

Choose a tag to compare

Changelog

  • CHANGED: Bumps the @hotwired/turbo to version ^7.0.1 for new installs

0.15.0

24 Sep 19:31
a0963e3

Choose a tag to compare

Changelog

  • CHANGED: Changed the default JS scaffolding (for new applications using php artisan turbo:install)
  • CHANGED: Bumps Turbo to final 7.0.0 version and Stimulus to the final 3.0.0 version
  • FIX: Bumped the Livewire bridge to install the latest 0.1.4 version, which fixes the issue with entangle

0.14.0

15 Sep 23:04
de38ac1

Choose a tag to compare

Changelog

  • CHANGED: Bumps @hotwired/turbo to RC.4 on new installs

0.13.0

15 Sep 00:12
bba76fb

Choose a tag to compare

Changelog

  • CHANGED: updated the JS scaffolding to add a resources/js/libs folder with a file for each lib. New installs should be more organized this way (I think)
  • CHANGED: updated @hotwired/turbo to the latest RC3
  • CHANGED: updated Stimulus imports and installs. The package moved from stimulus to @hotwired/stimulus.
  • CHANGED: tweaked the install command so it generates a more organized initial setup.

0.12.0

23 Jul 21:19
b1f3314

Choose a tag to compare

Changelog

  • NEW: there is a new request macro request()->wasFromTurboNative(), which can be used in content negotiation (#30)

0.11.2

23 Jul 03:30
e83d033

Choose a tag to compare

Changelog

  • CHANGED: Replaces the usage of simplexml_load_string with DOMDocument and DOMElement in the Turbo Stream testing helpers (#28)