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

@asteasolutions/tapestry-viewer

v0.1.1

Published

Prebuilt static Tapestry Viewer web app, ready to be served by a host application

Readme

@asteasolutions/tapestry-viewer

A prebuilt, static build of the Tapestry Viewer — a read-only web app for viewing Tapestry ZIP exports. The package contains only static files (dist/), has no runtime dependencies and can be served from any path by any web server or web framework.

Install

npm install @asteasolutions/tapestry-viewer

Serving the viewer

All asset URLs are relative, so you only need to serve the contents of node_modules/@asteasolutions/tapestry-viewer/dist under a path of your choice, e.g. /viewer/.

Always link to /viewer/index.html (or at least /viewer/ with a trailing slash). Without the trailing slash the relative asset URLs resolve against the parent path and the viewer fails to load. Some dev servers (including Vite's) also don't serve index.html for directory URLs and fall back to the host app's own page, so /viewer/index.html is the only form that works everywhere.

Vite (with vite-plugin-static-copy v4+), works both in dev and in production builds:

viteStaticCopy({
  targets: [
    {
      src: 'node_modules/@asteasolutions/tapestry-viewer/dist/**/*',
      dest: 'viewer',
      // Strip the `node_modules/@asteasolutions/tapestry-viewer/dist` prefix but keep `assets/`
      rename: { stripBase: 4 },
    },
  ],
})

Other stacks with a public/ directory: copy the files there, e.g. with a script in the host app's package.json so they stay in sync with the installed version:

"scripts": {
  "copy-viewer": "rm -rf public/viewer && cp -r node_modules/@asteasolutions/tapestry-viewer/dist public/viewer",
  "predev": "npm run copy-viewer",
  "prebuild": "npm run copy-viewer"
}

Consider adding public/viewer to .gitignore.

Express:

import { dirname } from 'node:path'
import { createRequire } from 'node:module'

const require = createRequire(import.meta.url)
const viewerDir = dirname(require.resolve('@asteasolutions/tapestry-viewer/dist/index.html'))
app.use('/viewer', express.static(viewerDir))

Usage

  • /viewer/index.html — shows an import screen where the user can drop a Tapestry ZIP.
  • /viewer/index.html?source=<url> — loads the Tapestry ZIP at <url> directly. The URL must be reachable from the browser (same origin or CORS-enabled).

The viewer is designed to fill the whole page, so to embed it inside another page use an <iframe>:

<iframe
  src="/viewer/index.html?source=/exports/my-tapestry.zip"
  style="width: 100%; height: 600px; border: 0"
></iframe>

The last opened Tapestry is cached in the browser's IndexedDB (database tapestry), scoped to the origin the viewer is served from.