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

@ko1265/file-preview-kit-web-components

v1.0.0

Published

Standalone Web Components file preview element for remote URLs.

Downloads

297

Readme

@ko1265/file-preview-kit-web-components

Standalone Web Components wrapper for file-preview-kit.

What it contains

  • registerFilePreviewElement
  • the file-preview custom element
  • request configuration support through attributes and the requestConfig property

Install

pnpm add @ko1265/file-preview-kit-web-components

Browser-only note

This package is browser-only / client-only.

  • Do not execute it on a pure Node.js path
  • In SSR frameworks such as Next.js or Nuxt, keep it behind a clear client boundary

Usage

import { registerFilePreviewElement } from "@ko1265/file-preview-kit-web-components";

registerFilePreviewElement();

const preview = document.createElement("file-preview");
preview.setAttribute("src", "https://example.com/readme.md");
document.body.append(preview);

For simple HTML embedding:

HTML embedding still requires a one-time registerFilePreviewElement() during app bootstrap. A <file-preview> tag alone is not enough until the custom element has been registered.

<file-preview
  src="https://example.com/private.pdf"
  credentials="include"
  auth-token="token-value"
  auth-scheme="Bearer"
  headers='{"X-Document-Scope":"private"}'
></file-preview>

Notes

  • Remote preview still depends on the browser being able to fetch the file source. For reliable production use, prefer same-origin files, controlled object storage/CDN with correct CORS, or a backend proxy.
  • Use the requestConfig property when you need structured request options such as auth tokens or Office workbook limits.
  • Attribute-based configuration is useful for simple HTML usage, but the property API is the more complete integration surface.
  • Request headers and auth settings only affect fetch-based previewers, not native media elements.
  • The custom element emits file-preview:loadstart, file-preview:load, and file-preview:error events so host apps can track loading state or surface failures.

Minimal event example:

preview.addEventListener("file-preview:loadstart", () => {
  console.log("preview loading");
});

preview.addEventListener("file-preview:load", () => {
  console.log("preview loaded");
});

preview.addEventListener("file-preview:error", (event) => {
  console.error("preview failed", (event as CustomEvent).detail);
});