Comment #⁨4⁩

In reply to Toby Toby

@Toby I'm currently using Livewire alongside Waterhole but after reading this, I am considering switching to Hotwire.

I started my project off with the Waterhole Skeleton Repo (composer create-project waterhole/waterhole), and I was considering installing Turbo-Laravel as a package rather than relying on the version Waterhole/core is using (so I could update to the latest version of Turbo-Laravel faster than relying on Waterhole updating it's dependencies).

My question is, do you think that's a wise idea? My concern is that having two versions of Hotwire could cause issues.

  1. Toby Toby Waterhole Founder Jul 23, 2024
    In reply to Stormlight Stormlight

    In general, yes, it's wise to add a package you explicitly depend on to your project's composer.json file, rather than assuming that it is included via one of your other dependencies. This way you can specify your own version constraint, and then if there is an incompatibility between the version you depend on and the version Waterhole depends on, Composer will yell at you.

    If you want to depend on a version of the package that Waterhole is not compatible with, then you would need to either wait for Waterhole to update or separate Waterhole into its own project.