Current Volt cannot be used with released phoenix_vapor (oxc/vize range mismatch)

[luis1112]

Volt 0.17.10 cannot be installed together with the released phoenix_vapor (0.3.0), because the two pin different ranges of the shared Rust NIFs:

	volt 0.17.10	phoenix_vapor 0.3.0
oxc	~> 0.17.7	~> 0.11.0
vize	~> 0.14.0	~> 0.10.0

Because "your app" depends on "phoenix_vapor ~> 0.3" which depends on
"volt ~> 0.10.1", "volt ~> 0.10.1" is required.
So, because "your app" depends on "volt ~> 0.17", version solving failed.

Pinning Volt back to ~> 0.10.1 to match Vapor is not an option for us either: any Volt below 0.11.1 requires reach ~> 1.6, and our project is on reach ~> 2.x.

The practical effect is that a Phoenix project cannot use a current Volt and write Vue components at the same time. Volt alone compiles .vue files, but the LiveView bridge lives in Vapor.

We landed on Volt 0.14.0 plus the inertia-inspired-foundations branch of phoenix_vapor, which resolves and works — but that means staying a minor behind and depending on a branch rather than a release.

Filed the matching issue on the Vapor side: elixir-volt/phoenix_vapor#2

Is a Volt release line intended to stay compatible with phoenix_vapor, or is the Vue-with-LiveView path expected to track Volt separately?

[luis1112]

Worth noting: examples/demo does run, but its mix.lock pins the older combination — volt 0.10.1, oxc 0.11.0, vize 0.10.0. As a fresh standalone project it has nothing to conflict with, so it does not exercise this problem.

The conflict shows up when adding phoenix_vapor to an existing Phoenix app that already tracks a current Volt, or that depends on packages incompatible with the old pins. In our case the app is on reach ~> 2.x, and any Volt below 0.11.1 requires reach ~> 1.6, so pinning back to the demo's versions is not available to us.