euv-cli 0.4.2

euv-cli

Official Documentation

Api Docs

The official CLI tool for the euv UI framework, providing run/build/fmt modes with hot reload and wasm-pack integration.

Installation

cargo install euv-cli

Usage

The CLI uses the pattern euv <action> where:

• Action: run (build + start server), build (build only), or fmt (format euv macros)

All wasm-pack build arguments are transparently forwarded after --.

Run (build + dev server)

# Build and start dev server with hot-reload
euv run -- --target web --out-name euv

# Build and start dev server with custom crate path and port
euv run --crate-path ./example --port 3000 -- --target web --out-name euv

# Release build with dev server
euv run --crate-path ./example -- --release --target web --out-name euv

# Use a custom static assets directory instead of the default "www"
euv run --www-dir public -- --target web --out-name euv

Fmt (format euv macros)

Format euv macro invocations (html!, class!, css_vars!, watch!) in Rust source files:

# Format all .rs files in the current directory (recursive)
euv fmt

# Format all .rs files in a specific directory
euv fmt --path ./src

# Format a single file
euv fmt --path src/main.rs

# Check if formatting is needed without modifying files
euv fmt --check

# Check a specific path
euv fmt --path ./src --check

Formatting Rules

• Tag name and { separated by exactly one space
• Attribute name immediately followed by :, then one space before the value
• if { expr } / match { expr } / for pattern in { expr } with proper spacing
• => in watch! macros with proper spacing
• Content inside expression braces { expr } is preserved verbatim; only template-level whitespace is normalized

Fmt Options

Build (build only)

# Dev build
euv build -- --target web --out-name euv

# Release build
euv build -- --release --target web --out-name euv

# Build with custom crate path and static directory
euv build -- --release --crate-path ./example --www-dir public -- --target web --out-name euv

Via Cargo

Run (build + dev server)

cargo run -p euv-cli -- run --crate-path ./example --port 3000 -- --target web --out-dir www/pkg --out-name euv

# Custom static directory
cargo run -p euv-cli -- run --crate-path ./example --www-dir public -- --target web --out-name euv

Build (build only)

cargo run -p euv-cli -- build --crate-path ./example -- --release --target web --out-dir www/pkg --out-name euv

Fmt (format euv macros)

# Format euv macros
cargo run -p euv-cli -- fmt --path ./example

# Check formatting
cargo run -p euv-cli -- fmt --check --path ./example

Options

How --www-dir Works

The --www-dir option controls where the CLI looks for and generates static assets:

• index.html is generated inside {crate-path}/{www-dir}/
• WASM artifacts are placed in {crate-path}/{www-dir}/pkg/ by default (unless overridden by --out-dir)
• Dev server serves files under the /{www-dir}/ route prefix
• JS import path in index.html is automatically computed relative to the www directory

For example, with --www-dir public:

example/
├── public/           ← static assets directory
│   ├── index.html    ← generated HTML
│   └── pkg/          ← WASM build output
│       ├── euv.js
│       └── euv_bg.wasm

wasm-pack Options (transparent passthrough after --)

All wasm-pack build flags are forwarded as-is. Common options:

See wasm-pack build --help for the full list of options.

License

This project is licensed under the MIT License. See the LICENSE file for details.

Contributing

Contributions are welcome! Please open an issue or submit a pull request.

Contact

For any inquiries, please reach out to the author at root@ltpp.vip.