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

@v-office/sdk-core

v1.24.2

Published

Core SDK for vOffice

Readme

@v-office/sdk-core

Shared core SDK for vOffice website-facing packages.

This package owns backend-independent domain contracts, shared parser utilities, runtime wiring, translations, and the v10 adapter implementation used by @v-office/website-sdk.

Development

Install dependencies (once, at the repository root; this package is a workspace member):

pnpm install

Run static checks:

pnpm check

Build distributable output:

pnpm build

sdks/website depends on this package through workspace:*; pnpm pack writes the exact core version into its tarball, so the two release together.

Publishing

See docs/internal/releasing/overview.md. node .github/release/cli.mts prepare sdk-core <bump> bumps core and website-sdk (it depends on core at runtime through workspace:*; pnpm pack writes the exact core version into its tarball) and scaffolds the notes of both; the Release packages workflow publishes what is on main, core first. Publishing only affects external consumers: the portals (portals/owner, portals/guest) embed the core of the deployed commit via workspace:*, so every core change on main reaches them on the next Build & deploy, with or without a release.