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

@microscope-js/core

v0.1.5

Published

Framework-agnostic core for microscope-js: Renderer interface + registry + mount() entry point

Downloads

852

Readme

@microscope-js/core

npm Bundle Types Provenance

The framework-agnostic heart of microscope-js. One Renderer interface, one Registry, one mount(). Everything else is a plugin.

Install

pnpm add @microscope-js/core @microscope-js/renderer-pdf

You almost never use core alone — pair it with one or more @microscope-js/renderer-* packages.

Use

import { createRegistry, mount } from '@microscope-js/core';
import { pdfRenderer } from '@microscope-js/renderer-pdf';
import { imageRenderer } from '@microscope-js/renderer-image';

const registry = createRegistry([pdfRenderer, imageRenderer]);

const handle = await mount({
  source: fileInput.files[0],            // File | Blob | ArrayBuffer | Uint8Array | URL | string
  container: document.getElementById('viewer')!,
  registry,
});

// later, when navigating away
handle.destroy();

mount() normalizes the source, sniffs the MIME type if needed, picks the highest-priority renderer that claims it, clears the container, and renders.

API

createRegistry(renderers)

Build a Registry from a list of Renderers. Later entries win by default; pass { renderer, priority } to override.

composeRegistries(...registries)

Merge multiple registries — useful when an app layers custom renderers on top of defaults without losing tree-shakability.

mount(opts): Promise<RenderHandle>

| Option | Type | Description | | ------------- | --------------------------------- | ----------- | | source | Source | What to render — File, Blob, ArrayBuffer, Uint8Array, URL, or string URL | | container | HTMLElement | DOM node to mount into. Cleared before render. | | registry | Registry | Where to look up the renderer | | options? | Record<string, unknown> | Per-render options, forwarded to the matched renderer | | signal? | AbortSignal | Cancels in-flight rendering | | rendererId? | string | Force-pick a renderer by id (skips matching) | | t? | (key, fallback) => string | Translation hook for user-facing strings |

Returns a RenderHandle with a required destroy() and optional renderer-specific capabilities (e.g. pageCount / scrollToPage from PDF, sheetNames / showSheet from XLSX).

Define your own renderer

import type { Renderer } from '@microscope-js/core';

export const myRenderer: Renderer = {
  id: 'myformat',
  name: 'My format',
  mimes: ['application/x-myformat'],
  extensions: ['myf'],
  async render({ source, container, signal }) {
    // …draw `source.blob` into `container`, honor `signal` for cancellation
    return {
      destroy() { /* clean up */ },
    };
  },
};

Renderers are plain values — no class instantiation, no global state. The registry handles matching by MIME + extension, with an optional canRender() override for byte-sniffing.

Re-exports

For convenience the core barrel also exports MicroscopeError, Source, NormalizedSource, normalizeSource, sniffMime, and extOf from @microscope-js/utils — so simple consumers don't need a second install.

See also

License

MIT