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

@platformos/platformos-check-node

v1.1.0

Published

This is the Node.js wrapper of the runtime-agnostic [`@platformos/platformos-check-common`](https://npm.im/@platformos/platformos-check-common) package. It comes with batteries included.

Readme

@platformos/platformos-check-node

This is the Node.js wrapper of the runtime-agnostic @platformos/platformos-check-common package. It comes with batteries included.

See the @platformos/platformos-check-common README for more details.

Entrypoints

| Function | Use | |---|---| | check(root, configPath?) | Lint a whole project on disk; returns Offense[]. | | appCheckRun(root, configPath?, log?) | Same, but also returns the resolved App and Config. | | checkAndAutofix(root, configPath?) | Lint then apply safe autofixes to disk. | | lintBuffer(params) | Lint a single in-memory buffer in the context of its on-disk project. |

lintBuffer — lint one buffer with project overlay

lintBuffer is the typed seam an embedding tool (e.g. the MCP supervisor) lints through — a direct library call, not an LSP and not a subprocess. It loads the project from disk so cross-file checks (MissingPartial, MissingPage, TranslationKeyExists, …) resolve against real files, overlays the buffer under edit in memory so the unsaved content is what gets linted and cross-referenced, and returns the structured check-common Offense[] for that file with fix / suggest and every typed field intact — no message-string round-trip.

It also reports whether it checked the file at all. Three kinds of path are never linted, and an empty offenses for one of them does not mean the file is fine:

| status | meaning | |---|---| | checked | The checks ran. offenses is the complete answer. | | excluded-by-config | The project's .platformos-check.yml ignore list covers this path. | | misplaced-source | A platformOS source (.liquid, .graphql, .yml) outside every deployed subtree — almost always a mistake. | | not-a-platformos-file | Not a platformOS source at all: not deployed, and nothing here parses it. | | not-a-source-file | An app file with no parser or checks — an asset (.js, .css, an image). |

import { lintBuffer } from '@platformos/platformos-check-node';

const { status, offenses } = await lintBuffer({
  root: '/abs/path/to/project',                 // project root (absolute)
  filePath: '/abs/path/to/project/app/views/pages/contact.liquid', // file under edit (absolute)
  content: editorBufferContents,                // unsaved buffer
  // configPath?: explicit config; resolved from root when omitted
});

if (status !== 'checked') {
  // Nothing was validated — say so rather than reporting "no problems".
}

for (const offense of offenses) {
  offense.check;     // e.g. 'MissingPartial'
  offense.severity;  // Severity
  offense.start.index; offense.end.index; // 0-based offsets
  offense.fix;       // optional Fixer (safe autofix)
  offense.suggest;   // optional Suggestion[] (manual fixes)
}

When filePath already exists in the project its on-disk source is replaced by the buffer; when it is new (not yet saved) the buffer is added so it is still linted. Only offenses for the buffer's file are returned.

License

MIT.