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

@homecloud-platform/sdk

v0.5.20

Published

HomeCloud Functions SDK for Node.js (ADR-033 / ADR-025e)

Downloads

920

Readme

@homecloud-platform/sdk (Node.js)

Part of the homecloud-sdk monorepo — Python at repo root; Node in js/.

Expectation: Node supports the same product surface as Python (homecloud-sdk), released under the same v* version. See PARITY.md.

Shipped as of 0.5.0: SO / MQ / Secrets / Mail / Functions / Apps / Accounts / Queues, typed errors, fromEnv / fromProfile / fromCredentials / fromSts / fromFunctionContext, console login helpers.

Install

npm install @homecloud-platform/sdk

From a local checkout (lab / layers):

{
  "dependencies": {
    "@homecloud-platform/sdk": "file:../../../homecloud-sdk/js"
  }
}

Usage (MVP — STS + SO)

const { HomeCloud } = require("@homecloud-platform/sdk");

exports.handler = async (event, context) => {
  const client = HomeCloud.fromSts(context.sts.archive, {
    accountId: context.account_id,
  });
  await client.so.putJson("my-bucket", "proof/ok.json", { ok: true });
  await client.so.upload("my-bucket", null, {
    body: Buffer.from("..."),
    key: "videos/clip.mp4",
    contentType: "video/mp4",
  });
  return { ok: true };
};

Unified release (Python + Node)

One tag publishes both registries with the same version:

./scripts/bump-version.sh 0.5.0
git add pyproject.toml js/package.json
git commit -m "Release 0.5.0"
git push origin HEAD
git tag v0.5.0
git push origin v0.5.0

| Registry | Package | Trigger | |----------|---------|---------| | PyPI | homecloud-sdk | tag v0.5.0 | | npm | @homecloud-platform/sdk | same tag v0.5.0 |

Workflows sync the version from the tag before publish (Trusted Publishing / OIDC).

Optional npm-only hotfix (no PyPI): js-v0.5.1.

One-time npm setup

  1. Org homecloud-platform on npm.
  2. First publish once locally: cd js && npm publish --access public
  3. Package → Trusted Publisher → GitHub Actions:
    • Org HomeCloudLab, repo homecloud-sdk
    • Workflow: publish-npm.yml
    • Environment: npm
  4. GitHub → Environments → create npm (and pypi already for Python).