puro and fvm
How spmx coexists with Flutter version managers.
A shim finds the real tool by removing ~/.spmx/shims from PATH and running the next match. That works with puro, fvm, asdf, mise and xcodes without configuration.
Order matters
~/.spmx/shims must come before the directory that holds your flutter, xcodebuild and swift. spmx setup puts it first, and spmx doctor verifies it.
puro
puro flutter ... runs the SDK directly, so it bypasses the flutter shim. The xcodebuild shim still applies to the builds it triggers, so Apple Swift package builds are still cached. Use plain flutter (with puro's environment on PATH) for the full behavior. spmx doctor reports whether it detected puro after the shims.
fvm
Put fvm's active SDK bin directory on PATH after ~/.spmx/shims, or run fvm flutter knowing it takes the same direct route as puro.
Bypassing
SPMX_DISABLE=1 flutter run