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

screenshot-studio-backend-sdk

v0.1.39

Published

Typed server SDK for the Screenshot Studio Go backend

Readme

Screenshot Studio backend SDK

Typed TypeScript client for the Go backend's APIs: workspaces, assets, designs, projects, presets, brand kits, share links, integrations, publishing, and social OAuth. Build with npm run build in this directory. The package exports JavaScript and type declarations from dist; npm pack --dry-run verifies the release artifact.

The app compiles this package from source: tsconfig.json maps screenshot-studio-backend-sdk to src/index.ts, so a backend endpoint and its client ship in one pull request. The Next.js server reaches it through lib/backend/sdk.ts; UI calls remain on same-origin tRPC routes.

Instantiate only in a trusted server process. The client sends a private PUBLISHING_SERVICE_TOKEN and the current session ID. The Go API validates that session and its workspace role from the shared database before each operation. Never put the service token in browser code or NEXT_PUBLIC_* env.

Scheduled post status includes UNKNOWN_DELIVERY, which requires remote reconciliation before any retry.

Releasing

CI publishes the package; nobody runs npm publish. Bump version in this package.json in the pull request that changes the SDK. The Publish SDK workflow (.github/workflows/publish-sdk.yml) fails a pull request that changes the SDK without a new version, and publishes the new version when the change reaches main, for consumers outside this repository. The app itself uses the source, so it needs no reinstall.

The workflow authenticates with npm trusted publishing, and only from main: its publish job runs in the npm GitHub environment, which deploys from main alone, and npm trusts only that environment. On npmjs.com, the package's trusted publisher is GitHub Actions, PlaybookMediaLLC/screenshot-studio, workflow publish-sdk.yml, environment npm. Do not add an npm token as a repository secret: any branch could read it.