Round two of fixing #124

This time, the path was being canonicalized in another location. My
original verification apparently did not account for this.

All calls to `canonicalize` have been audited, and every location where
such is called, it is also expected that the path exist, and is indeed
considered an error if it does not exist.

CHANGELOG.md

@@ -6,7 +6,7 @@ Subheadings to categorize changes are `added, changed, deprecated, removed, fixe
 
 ## Unreleased
 
-## 0.8.1
+## 0.8.2 & 0.8.1
 ### fixed
 - Fixed [#124](https://github.com/thedodd/trunk/issues/124) where path canonicalization was being performed on a path which did not yet exist, and as it turns out was already in canonical form.
 

Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "trunk"
-version = "0.8.1"
+version = "0.8.2"
 edition = "2018"
 description = "Build, bundle & ship your Rust WASM application to the web."
 license = "MIT/Apache-2.0"

src/pipelines/rust_app.rs

@@ -99,10 +99,7 @@ impl RustApp {
     async fn cargo_build(&mut self) -> Result<(PathBuf, String)> {
         self.progress.set_message(&format!("building {}", &self.manifest.package.name));
         if let Some(chan) = &mut self.ignore_chan {
-            let target_dir = async_std::fs::canonicalize(&self.manifest.metadata.target_directory)
-                .await
-                .context("error taking canonical path to cargo target dir")?;
-            let _ = chan.try_send(target_dir.into());
+            let _ = chan.try_send(self.manifest.metadata.target_directory.clone());
         }
 
         // Spawn the cargo build process.