···33 * It might be better to use a more sophisticated approach, using some sort of diffing, handling reconnecting, etc.
44 */
5566-import { AnsiUp } from "./vendor/ansi_up";
66+import { AnsiUp } from "ansi_up";
77import { createErrorOverlay } from "./overlay";
88import { error, log } from "./utils";
99···32323333const socket = new WebSocket(`ws://${WS_SERVER_ADDRESS}/ws`);
34343535-socket.addEventListener("open", (event) => {
3535+socket.addEventListener("open", () => {
3636 console.log("Connected to server");
3737 socket.send("Hello Server!");
3838});
···11-# Vendored libraries for the Maudit CLI dev server.
22-33-Since the JS part of the Maudit CLI is built at build time through a Rust build script, we cannot rely on a package manager to fetch dependencies, as people downloading the Maudit CLI from crates.io won't have access to npm, pnpm, yarn, etc.
44-55-As such, we vendor the dependencies we need here. They are copied as-is from their respective repositories and include their license information at the top of the file.
66-77-An alternative to this approach would be to pre-bundle the JS code and ship the bundled version with the crate, but it's a lot more cumbersome in development so while things are still evolving, we prefer this approach.