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-docu-builder

v0.2.2

Published

CLI and API to build WinCC OA project documentation via WCCOActrl and buildHelp.ctl

Readme

npm-winccoa-docu-builder

Build WinCC OA project documentation using WCCOActrl and the bundled non-runnable DocuBuilder subproject (buildHelp.ctl).

Correct project model

  1. Register DocuBuilder as a non-runnable WinCC OA project.
  2. Register the worker / source project (e.g. Squirt) as runnable, with DocuBuilder attached via --sub-project DocuBuilder (@winccoa-tools-pack/npm-winccoa-register-project).
  3. Optionally merge external projectDocu asset directories into the worker data/projectDocu (theme CSS, advanced documentation config, extras).
  4. Start CTRL against the worker config (not -proj DocuBuilder):
WCCOActrl -config <worker>/config/config -n -log +stderr buildHelp.ctl <CompanyName>

Why this is correct:

  • The worker project owns logs and help output (not DocuBuilder).
  • getPath / script resolution uses DocuBuilder as a sub-project.
  • Docs assets can live outside the productive tree and still be discovered by OA next to advanced config.
  • v1 builds docs from the runner/worker project only (tests later).

Install

npm install @winccoa-tools-pack/npm-winccoa-docu-builder

CLI

# Register only (DocuBuilder + worker with sub-project)
winccoa-docu-builder register ./src/Squirt -v 3.21

# Build docs (registers first by default)
winccoa-docu-builder build ./src/Squirt -v 3.21 -c "winccoa-tools-pack"

# Layer external projectDocu sources (repeatable; left to right)
winccoa-docu-builder build ./src/Squirt -v 3.21 \
  --project-docu ./.documentation-theme \
  --project-docu ./.winccoa-docu-builder

projectDocu merge rules

Sources are copied into {worker}/data/projectDocu before the build:

| File | Policy | | --- | --- | | Advanced config fragment | Concatenate in path order (later keys win) | | Other top-level files (extra_*.html, extra_stylesheet.css, ...) | Last path wins |

Local registration helpers

Shell (Linux / Git Bash / CI):

./scripts/register-docubuilder-projects.sh \
  --project-path ./src/Squirt \
  --version 3.21 \
  --langs en_US.utf8

PowerShell (Windows local):

./scripts/register-docubuilder-projects.ps1 `
  -ProjectPath ./src/Squirt `
  -Version 3.21

API

import {
  buildDocs,
  mergeProjectDocuSources,
  registerWorkerProjectWithDocuBuilder,
} from '@winccoa-tools-pack/npm-winccoa-docu-builder';

await registerWorkerProjectWithDocuBuilder({
  projectPath: './src/Squirt',
  version: '3.21',
});

const result = await buildDocs({
  projectPath: './src/Squirt',
  version: '3.21',
  companyName: 'winccoa-tools-pack',
  registerProject: false,
  projectDocuPaths: [
    './.documentation-theme',
    './.winccoa-docu-builder',
  ],
});

DocuBuilder layout

winccoa/DocuBuilder/
  scripts/buildHelp.ctl

DocuBuilder is non-runnable. It has no config/ or log/. The worker project owns config/config, logs, and help when CTRL runs with -config.

GitHub Action

Use winccoa-tools-pack/github-actions-winccoa/actions/winccoa-docu-builder to run this package in CI with warning extraction and PR annotations. Pass multi-line project-docu-paths to layer external asset directories.

Development

npm ci
npm run build
npm run test:unit