Dependency conflicts with Trunk 0.7.0+

[MartinKavik]

Command + Error:

$ trunk serve
Error during execution of `cargo metadata`: error: package collision in the lockfile: packages seed v0.7.0 (C:\work\repos\seed) and seed v0.7.0 (C:\work\repos\stremio-seed-poc\../seed) are different, but only one can be written to lockfile unambiguously
 server running at http://127.0.0.1:8080/
   trunk | error

• C:\work\repos\seed and C:\work\repos\stremio-seed-poc\../seed points to the same folder, but it's marked as a conflict.
• Trunk 0.6.0 builds the app without problem. So the bug was introduced probably in Trunk 0.7.0.
• Perhaps it's related to Cargo fails to compile a crate if it's included multiple times at different paths rust-lang/cargo#8639 or Relative path crate dependencies are canonicalized badly on windows rustwasm/wasm-pack#380.
• Tested on:
  • Windows 10 + git bash
  • Trunk 0.6.0, 0.7.0, 0.7.2
  • rustc 1.47.0 (18bf6b4f0 2020-10-07)
  • wasm-bindgen 0.2.68
  • A client's app based on Seed.

[thedodd]

Hmmm, I'll definitely investigate, but I'm skeptical that it is a Trunk issue. Trunk doesn't do anything with dependencies, its own dependencies have no impact on a user's project. Based on the error output, it looks like Seed has a dependency issue in its own lockfile.

Does a normal cargo build --target=wasm32-unknown-unknown && a normal cargo metadata work as expected for your project? Trunk just calls cargo, it shouldn't have an impact on this sort of stuff.

If it is an issue with Trunk, it would only be related to the way cargo is called.

[thedodd]

Based on some offline discussion, it appears as though this may be a Windows specific issue ... as the same problem is not taking place in *nix environments. More investigation is needed.

[MartinKavik]

Investigation in README: https://github.com/MartinKavik/trunk-debug-deps
I'll create a PR with fix.