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

@mosetta/ide-client

v0.0.14

Published

The Mosetta IDE client: the core that brings plugins up, and `mount()` to put the IDE into any element of a page.

Readme

Client

@mosetta/ide-client · The Mosetta IDE client: the core that brings plugins up, and mount() to put the IDE into any element of a page.

What it does

The half of the IDE that runs in the browser — and it is small on purpose. It owns the socket to the daemon, the session, the plugins' home, the registry of declarations, the settings layers, the dictionary and the frame. It has no commands, no panels and not one word about windows: everything visible is brought by plugins.

  • Brings plugins up: asks the daemon for the list, fetches each one's built code, constructs it, hands it its services and starts it. One plugin failing is a line in the notifications, not a dead editor.
  • Puts the shared libraries on one table: preact, the signals, CodeMirror and the contract exist in exactly one copy, which is why a plugin can import them.
  • Mounts anywhere: mount(element) runs the IDE inside an element of somebody else's page — keys, pointer events and styles stay inside it, and the page's title, address and scroll position are left alone.

You do not usually install this by hand: npx @mosetta/ide runs the whole IDE, and the native app builds this package on your machine.

Screenshots and demos

The IDE embedded in an ordinary page

ide.mosetta.org is this client, mounted into a landing page with a daemon the page plays itself.

Using it from another plugin

A plugin never imports the client: it is given what it needs through @mosetta/ide-api. The client is what an APPLICATION imports — a page that wants an IDE in it:

import { mount } from '@mosetta/ide-client/embed';

const ide = mount(document.querySelector('#ide')!, {
  // optional: anything shaped like a WebSocket, if the daemon is not the local one
  dial: () => new WebSocket('ws://127.0.0.1:4177/rpc'),
});

ide.commands.run('search.everywhere');

The element decides the size, so give it one. mount returns the core: commands to run anything by id, session for the open project, plugins for what came up. The package ships TypeScript sources and is built by the application's own bundler (Vite in this repository).