Currently, shuttle is in its own crate, however this begun to create a bit more complexity as time goes on due to having to maintain duplicate code. While we could split the duplicate code into its own crate, that would likely introduce additional cycles. The best solution here would be to migrate shuttle into warp-ipfs, which would reduce the dependency footprint and complexity while still introducing a binary that could be built.
Currently, shuttle is in its own crate, however this begun to create a bit more complexity as time goes on due to having to maintain duplicate code. While we could split the duplicate code into its own crate, that would likely introduce additional cycles. The best solution here would be to migrate shuttle into
warp-ipfs
, which would reduce the dependency footprint and complexity while still introducing a binary that could be built.