templates: move static assets to the templates crate

It makes more sense to keep CSS near the templates, and the
client-side JavaScript code too, since it depends on the DOM structure
to work. Additionally, the overhead of `include_dir!()` is almost
completely mitigated by the fact that this is a separate crate that
isn't recompiled often.

The linking stage, however, is still expected to take a little bit
long. But I doubt it'd be longer than what it was before, since it's
the same exact files that get linked into the app.

1 files changed, 0 insertions, 14 deletions

diff --git a/kittybox-rs/build.rs b/kittybox-rs/build.rs
index 3d4c62b..c639cf8 100644
--- a/kittybox-rs/build.rs
+++ b/kittybox-rs/build.rs
@@ -1,20 +1,6 @@
 fn main() {
     use std::env;
     let out_dir = env::var("OUT_DIR").unwrap();
-    println!("cargo:rerun-if-changed=javascript/");
-
-    if let Ok(exit) = std::process::Command::new("tsc")
-        .arg("--outDir")
-        .arg(std::path::Path::new(&out_dir).join("kittybox_js"))
-        .current_dir("javascript")
-        .spawn()
-        .unwrap()
-        .wait()
-    {
-        if !exit.success() {
-            std::process::exit(exit.code().unwrap_or(1))
-        }
-    }
 
     println!("cargo:rerun-if-changed=companion-lite/");
     let companion_out = std::path::Path::new(&out_dir).join("companion");