Call `vite` directly to build the frontend.

Calling through `npm` wasn't adding anything other than complexity, and it made it somewhat harder to follow what tools did what.

I'm also pretty sure `tools/build-ui` was totally unused.

This was originally part of [another proposal][pr-6]. I've broken it out to make the intent clearer, and to make the proposal easier to get a handle on in isolation from other, related changes. Thanks to @wlonk for their input on this!

[pr-6]: https://codeberg.org/ojacobson/pilcrow/pulls/6

Merges prop/build-without-npm into main.

1 files changed, 2 insertions, 2 deletions

diff --git a/build.rs b/build.rs
index 3b7abda..6d4805f 100644
--- a/build.rs
+++ b/build.rs
@@ -20,7 +20,7 @@ fn main() -> Result<(), io::Error> {
         )));
     }
 
-    // rerun `npm run build` whenever the UI changes.
+    // rerun `vite build` whenever the UI changes.
     //
     // `node_modules` is always touched if `npm install` runs, leading to spurious
     // rebuilds. (This duplicate is purely organizational; it reflects that the ui
@@ -32,7 +32,7 @@ fn main() -> Result<(), io::Error> {
     println!("cargo::rerun-if-changed=svelte.config.js");
     println!("cargo::rerun-if-changed=vite.config.js");
     println!("cargo::rerun-if-changed=ui");
-    let status = Command::new("npm").args(["run", "build"]).status()?;
+    let status = Command::new("npx").args(["vite", "build"]).status()?;
     if !status.success() {
         return Err(io::Error::other(format!(
             "'npm run build' exited with status {status:?}"