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

@mithril-inspector/adapter-kit

v0.3.3

Published

Shared, bundler-neutral option resolution and virtual-module utilities for Mithril Inspector's build-tool adapters (Vite, Rollup, ...).

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

erikvullingserikvullings

Keywords

mithrilmithril.jsdevtoolsinspectoradapterinternal

Readme

@mithril-inspector/adapter-kit

Shared, bundler-neutral pieces factored out of @mithril-inspector/vite so rollup, esbuild and webpack reuse them instead of copying them (ADR-004). Not a standalone integration by itself — every build-tool adapter still owns its own bundler-specific hook wiring (Vite's configResolved/transformIndexHtml/configureServer, Rollup's this.meta.watchMode, ...).

No bundler import of any kind (ADR-004): this package only depends on the other bundler-neutral core packages (overlay, protocol, runtime, server, transform).

What's here

  • resolveInspectorOptions (options.ts) — the full MithrilInspectorOptions surface plus mode and redact, resolved into a fully-defaulted ResolvedInspectorOptions, and four derived builders (toRuntimeBootstrapConfig, toOverlayOptionsInput, toServerOptions, toTransformOptions) that turn it into each dependency's own option shape.
  • ids.ts — the two virtual module specifiers (virtual:mithril-inspector/runtime / .../overlay) and their \0-prefixed resolved ids.
  • virtual-modules.ts — resolveVirtualId/loadVirtualModule plus the generated source of both virtual modules (runtimeModuleCode, overlayModuleCode): re-exporting the transform-facing runtime helpers, installing a configured runtime on the global hook, and mounting the shadow-root overlay.
  • module-filter.ts — shouldAttemptTransform, the coarse pre-filter every adapter's transform/load hook runs before calling into the shared transform: skip \0-prefixed virtual modules, node_modules, and the inspector's own packages (which import Mithril themselves and must never be instrumented recursively).
  • hmr-protocol.ts — HMR_INVALIDATE_EVENT/HmrInvalidatePayload (ADR-106): the wire-protocol constant the generated runtime bootstrap listens for. A dev-server adapter with real HMR (Vite, webpack) dispatches it; one without (Rollup and esbuild have no fine-grained HMR, only watch-mode rebuilds) simply never sends it — the constant is still shared so the generated bootstrap code is identical either way.

What's not here

Anything that needs a specific bundler's own API: Vite's HTML injection (transformIndexHtml/HtmlTagDescriptor), its dev server middleware registration (configureServer), and its real HMR event dispatch (handleHotUpdate) stay in @mithril-inspector/vite itself, since Rollup and esbuild have no equivalent hooks.