Svelte logo

svelte-utils

Test-drive self-contained .svelte components from a tiny, dependency-free CLI — against a self-hosted playground "core" running anywhere on your network.

⚠️ Not affiliated with the Svelte team. Independent open-source project that reuses the MIT-licensed playground from sveltejs/svelte.dev and the @sveltejs/mcp autofixer. All credit for those goes to the Svelte contributors.

What it does

Everything runs on the core, so client machines need nothing but the single-file CLI and Node 20+.

Setup — paste this into your agent

Copy the block below into a coding agent (or a terminal) on the machine you're setting up:

# Set up svelte-utils (https://github.com/davis7dotsh/svelte-utils)
# It has two parts: a "core" server (hosts the playground + autofix API)
# and a tiny dependency-free CLI. Do the following:

# 1. Install the CLI (requires Node 20+):
curl -fsSL https://davis7dotsh.github.io/svelte-utils/install.sh | sh
# It installs to ~/.local/bin/svelte-utils — make sure that's on PATH.

# 2a. IF this machine should HOST the core (Linux/systemd):
git clone https://github.com/davis7dotsh/svelte-utils
cd svelte-utils && pnpm install
svelte-utils daemon install          # builds + installs systemd service on 0.0.0.0:7488
sudo loginctl enable-linger $USER    # keep it alive after logout
# Config is auto-written to ~/.svelte-utils pointing at the local core.

# 2b. IF this machine is just a CLIENT of an existing core:
svelte-utils config set host http://CORE_HOSTNAME:7488   # <-- replace CORE_HOSTNAME

# 3. Verify:
printf '<h1>hello</h1>' > /tmp/Smoke.svelte
svelte-utils best-practices /tmp/Smoke.svelte # expect: no issues
svelte-utils open /tmp/Smoke.svelte --no-open # prints the playground URL

Everyday use

svelte-utils open Component.svelte             # live playground preview
svelte-utils best-practices Component.svelte   # autofixer suggestions
svelte-utils config                            # show current config
svelte-utils daemon status                     # core health (on the server)