npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wasm-idle/terminal

v1.0.7

Published

Svelte terminal component for wasm-idle playground bindings

Downloads

1,126

Readme

@wasm-idle/terminal

Optional Svelte/xterm terminal UI for a wasm-idle playground binding. Install it only in browser applications that render the terminal:

pnpm add wasm-idle @wasm-idle/terminal svelte
<script lang="ts">
	import Terminal from '@wasm-idle/terminal';
	import { createPlaygroundBinding } from 'wasm-idle';

	const playground = createPlaygroundBinding({
		rootUrl: 'https://cdn.example.com/wasm-idle'
	});
</script>

<Terminal {playground} />

Compiler and language-runtime payloads are not included in this package. Configure their external URLs through the injected playground binding.

Stop lifecycle

TerminalControl.stop() does not resolve until the active sandbox's kill() or terminate() operation resolves. Sandbox implementations may return either void or Promise<void> from those methods; an asynchronous implementation must keep its promise pending until runtime resources are released.

The C/C++ and Rust LLDB sandboxes use this contract to wait for both LLDB and WAMR worker teardown. Callers can therefore await stop() before launching another debug session without overlapping the previous session's workers or receiving its late events.

Interactive runs

Set interactive: true only for a run that remains under explicit user control and has a working stop/dispose path. The shared execution boundary then omits the wall-clock deadline only for the final run(..., prepare = false) call. Runtime loading and prepare() keep their configured deadlines, and AbortSignal cancellation, output/diagnostic limits, exclusive sandbox ownership, and teardown remain enforced. wasm-idle uses this contract for Debug runs, which may stay paused at a breakpoint indefinitely; ordinary Run requests remain time-bounded.

Input generations

Input submitted while prepare() is still running remains queued for the matching run() when the same language and runtime assets reuse that sandbox. stop(), clear(), destroy(), runtime restart, component teardown, and a language or asset change discard queued input and EOF state before retiring the sandbox. A later debug session therefore cannot consume stdin entered for an older generation. Clipboard reads are asynchronous, so pasted text is accepted only if the input generation that requested it is still current when the browser returns the clipboard contents.

The component prepares Fit, Unicode 11, and Web Links addons in parallel. Search and serialization addons are loaded only when a host calls loadSearchPlugin(terminal) or loadSerializePlugin(terminal) with its xterm instance. Existing registerAllPlugins(terminal) callers still receive all six addons.

The component uses xterm's default renderer. Pass <Terminal {playground} webgl /> to load the optional WebGL renderer after the terminal is ready; it falls back to the default renderer if a GPU context is unavailable. The standalone loadWebglPlugin(terminal) helper is also exported.