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

unslide

v0.1.1

Published

Code-first tooling for explicit fixed-page HTML reports and structurally validated PDF output.

Downloads

160

Vulnerabilities

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

Links

Git

Maintainers

sjuneparksjunepark

Keywords

reportshtmlpdfplaywrightreact

Readme

Unslide

Unslide builds explicit fixed-page reports from TypeScript, React, HTML, and CSS. The canonical artifact is standalone HTML; the same HTML can be captured in Chromium, exported to a structurally validated PDF, and inspected as target-native page images.

Reports own the complete document, geometry, styling, print rules, and content fit. Unslide owns only the nonvisual build, validation, capture, and export lifecycle. It does not paginate, move overflowing content, or prescribe a design system.

Install

Unslide currently supports pnpm projects in the environment documented by the delivery contract. Configure pnpm before installation:

# pnpm-workspace.yaml
engineStrict: true
allowBuilds:
  esbuild: true
  msgpackr-extract: false
pnpm add unslide
pnpm dlx [email protected] install chromium

Initialize a report project:

pnpm exec unslide init
pnpm exec unslide init --yes

The first command is a dry run. The confirmed command creates unslide.json, report.tsx, and removable starter report.css; it never overwrites files with different contents.

Build and inspect the report:

pnpm exec unslide build report
pnpm exec unslide inspect report
pnpm exec unslide capture report
pnpm exec unslide export report
pnpm exec unslide inspect-pdf report

capture and export consume existing HTML, and inspect-pdf consumes an existing PDF. Rebuild upstream artifacts after changing source. Export waits boundedly for static resources activated by print media, then checks PDF structure; it does not establish visual fidelity. Inspect every PDF-native page image. The tooling does not measure or repair content fit, although page-count validation can reveal unintended print fragmentation.

Authoring Contract

A report exports a complete React <html> document and marks each page with the versioned HTML artifact protocol. Ordinary values and collections flow into report source without a Unslide data model. Local assets can be explicitly inlined through unslide/react; recognized unresolved resource dependencies are rejected by the first-party writer.

HTML remains independently viewable without React, Node.js, Playwright, or a server. PDF and inspection images are derived delivery evidence, not parallel authoring formats.

Protocol v1 supports static visual resources. Animations, delayed client rendering, and an author-controlled asynchronous readiness signal are not supported inputs. Print color adjustment is report-owned CSS, and exact color reproduction across rendering environments is not guaranteed.

The project JSON Schema rejects unknown fields. Configuration loading additionally rejects paths that escape the project root and overlapping source and output paths. Visual choices do not belong in configuration.

CLI Automation Contract

With no command, unslide discovers the nearest unslide.json from the current directory or its parents and lists configured reports. htmlStatus: present|missing reports only whether the configured HTML path exists; it does not claim freshness.

Every invocation writes one TOON document to stdout:

| Exit | Meaning | |---|---| | 0 | Success or an idempotent no-op | | 1 | Operational failure | | 2 | Invalid command usage |

Default stderr is empty. Operational failures use an error record with a stable code, a concise message, and relevant structured context. The current operational codes are project-not-found, project-config-unreadable, project-config-invalid, report-not-found, artifact-not-found, artifact-invalid, browser-not-installed, and command-failed. Usage errors use code: usage with exit 2.

Top-level and per-command --help are noninteractive. Unknown flags and extra values still fail when combined with help; help bypasses only missing required values. Commands returned in help are complete and should be run as written.

| Option | Contract | |---|---| | --log-level <off\|info\|debug> | Overrides UNSLIDE_LOG_LEVEL; default off | | --full | Available only to inspect, capture, and export; removes authored-diagnostic truncation |

Default diagnostics show at most 10 issues and 1,000 Unicode characters per authored message or resource, with exact totals. --full never exposes raw dependency causes, but it may reveal complete report-authored text and resource identifiers.

Enabled logging writes newline-delimited Effect JSON to stderr while leaving TOON stdout unchanged. info records major phases; debug adds detailed lifecycle and Effect-cause evidence. Logging and --full output can contain local paths or authored content and should be handled as sensitive diagnostics.

Package Surface and Compatibility

The public package exposes only:

Browser sessions, validators, capture internals, and speculative adapter seams remain implementation details.

unslide.json version 1 and artifact protocol v1 are the persisted contracts. Unsupported versions fail with manual migration guidance; the CLI does not rewrite user-owned configuration or source. The package remains 0.x, so breaking public-contract changes require an explicit pre-1.0 minor release and migration note.

Repository Development

pnpm install --frozen-lockfile
pnpm exec playwright install chromium
pnpm run validate

Linked consumers execute compiled dist. After changing this repository's package source, run pnpm run build:package before using a link, or run pnpm pack --pack-destination .tmp/package and install the fresh tarball. The production CLI does not detect stale linked builds.

See the Repository Workflow for proof-report commands, generated artifacts, packed-consumer testing, and visual inspection requirements.

Repository-only documentation has one responsibility per file:

License

Unslide is available under the MIT License.