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

verben-workflow-ui

v0.5.95

Published

This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 18.2.0.

Readme

VerbenNgUi

This library was generated with Angular CLI version 18.2.0.

Workflow Designer

The visual workflow editor (<lib-workflow-designer>) is the largest and most intricate component in this library, and it has its own documentation set:

📖 Workflow Designer docs

Read the integration guide before embedding it; the module requires an ENVIRONMENT provider and a reachable Workflow API, and fails at construction without them.

Theming

This library is theme-aware: its component styles read the verben-ng-ui --vbn-* CSS custom properties instead of hardcoded colors, so it automatically follows whatever theme the host application configures. It ships no theme config of its own (no theme.css, no forRoot()) — that is the host app's job.

Host requirement: the consuming application must load node_modules/verben-ng-ui/styles/theme.css (which requires verben-ng-ui@>=1.3.0, matching this library's peer dependency). See that package's INTEGRATION.md for the full multi-layer setup. Colors unique to the workflow designer canvas are intentionally left as-is (they are functional diagram colors, not brand tokens).

Code scaffolding

Run ng generate component component-name --project verben-workflow-ui to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module --project verben-workflow-ui.

Note: Don't forget to add --project verben-workflow-ui or else it will be added to the default project in your angular.json file.

Build

Run npm run build:lib from the workspace root. Artifacts land in dist/.

Use the script, not a bare ng build verben-workflow-ui. The script runs two steps — the Angular build and a separate postcss pass (build:lib:styles) that compiles src/styles/styles.css into dist/. Skipping the second step produces a package that installs and imports cleanly but renders completely unstyled.

Publishing

After npm run build:lib, go to cd dist/verben-workflow-ui and run npm publish. Verify dist/verben-workflow-ui/styles/styles.css exists first — if it doesn't, the styles step didn't run.

Running unit tests

Run ng test verben-workflow-ui to execute the unit tests via Karma.

⚠️ The suite does not currently run. The Karma builder bundles every *.spec.ts in the workspace, and two broken specs fail the whole bundle. See the development doc for which specs and why it matters.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.