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

@winccoa-tools-pack/npm-winccoa-install-info

v0.1.0

Published

CLI to get basic information about installed WinCC OA versions and registered projects

Downloads

6

Readme

npm-winccoa-install-info

npm version License CI/CD Release

CLI (and thin library helpers) for WinCC OA installation and registered-project introspection.

Detection of installed versions and the project registry lives in @winccoa-tools-pack/npm-winccoa-core. This package is a small, scriptable facade — not a second discovery stack.

See docs/VISION.md for scope and JSON shapes.

Install

npm install -g @winccoa-tools-pack/npm-winccoa-install-info

Or run without a global install:

npx @winccoa-tools-pack/npm-winccoa-install-info --help

CLI

winccoa-install-info versions [--json|--no-json] [--result-file <path>]
winccoa-install-info projects [--json|--no-json] [--result-file <path>]

JSON is the default (best for scripts/CI). Use --no-json for a simple TSV table.

Core may print diagnostic logs to the console. For automation, prefer --result-file so the clean payload is written to a file (stdout is not used for the payload in that mode).

Examples

winccoa-install-info versions --json
winccoa-install-info projects --json
winccoa-install-info projects --result-file projects.json
winccoa-install-info versions --no-json --result-file versions.txt

Example projects item:

{
  "id": "MyPlant",
  "name": "MyPlant",
  "runnable": true,
  "installationPath": "D:/WinCC_OA_Proj/MyPlant",
  "winccOaVersion": "3.20",
  "currentProject": false
}

Optional fields when present in the registry: company, description, invalidReason.

Exit codes

| Code | Meaning | | ------ | --------- | | 0 | Success | | 1 | Usage / help | | 2 | Runtime failure |

Library

import {
  listVersions,
  listProjects,
} from '@winccoa-tools-pack/npm-winccoa-install-info';

const versions = listVersions();
const projects = listProjects();

For programmatic access inside Node apps, prefer core APIs directly when you do not need the CLI.

Related packages

| Package | Role | | --------- | ------ | | npm-winccoa-core | Install, version, component, and project-registry APIs | | npm-winccoa-install-info | This CLI (+ thin helpers) | | npm-winccoa-register-project | Register / unregister projects |

Development

npm ci
npm run build
npm run test:unit
npm run test:integration

Requires Node.js 20+.

Try the CLI against your machine

After a build, run the compiled entry (no global install needed):

node dist/cjs/cli.js --help
node dist/cjs/cli.js versions
node dist/cjs/cli.js projects
node dist/cjs/cli.js versions --no-json

Optional: npm link so winccoa-install-info is on your PATH, or use npx tsx src/cli.ts … without rebuilding.

Full contributor workflow (link/unlink, exit codes, empty-host behavior): see CONTRIBUTING.md.

Docs index

| Doc | Contents | | --- | -------- | | docs/VISION.md | Product scope | | docs/automation/CI-INTEGRATION.md | Package CI knobs; workflows are source of truth | | docs/automation/GITFLOW_WORKFLOW.md | Short pointers to APM git-flow / related skills |

Org process lives in APM skills (apm install → .github/skills/), not duplicated long template docs.