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

@ossy/platform

v0.0.1-alpha.2

Published

Platform module: deployment platform config resource template and home UI for Ossy websites

Downloads

177

Vulnerabilities

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

Links

Git

Maintainers

oskarssylwanoskarssylwan

Keywords

Readme

@ossy/platform

Ossy Platform module: resource template @ossy/platform/config (mirrors deployment-tools platform-config.json) and the platform home UI (PlatformHomeBody, metadata for routing).

Install

npm install @ossy/platform

Peer dependencies (your app should already include them):

  • react
  • @ossy/connected-components (for usePageShell on module pages)
  • @ossy/design-system
  • @ossy/router-react
  • @ossy/sdk-react

Use in a website

  1. Spread PlatformResourceTemplates into your app resourceTemplates (and sync to the API via publish / cms upload).
  2. Add @ossy/platform to modules in src/config.js so src/platform/home.page.js is picked up (JSX-free so Rollup can parse .page.js; *.page.jsx works under src/ for other files if the bundler accepts JSX there).
  3. Add src/page-shell.jsx (or .js) that default-exports your site layout (e.g. ossy.se re-exports Layout). Module pages call usePageShell() so they do not depend on site paths.
  4. Register Definition in your navigation / module registry.

Surface in this package: *.page.* files may live anywhere under src/; resources are exported from the package root (PlatformResourceTemplates, constants). API routes and worker tasks can follow the same *.api.js / *.task.js conventions under the site src/ today; pulling those from installable modules can mirror modules later (e.g. shared discovery for APIs / worker tasks).

Publishing

Released on its own semver from this monorepo (lerna publish with independent versions). Bump @ossy/platform when only this module changes.

Direction

Long term, which modules a workspace may enable should be driven by the CMS and tied to billing / entitlements. Packages stay the distributable implementation of each module; access control lives in the product, not in npm scope alone.