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

enso-workflow-builder

v0.1.10

Published

Angular 20 library. Sources are compiled from `src/app` via symlink `projects/enso-workflow-builder/src/lib` → `../../../src/app`.

Readme

Enso workflow builder (npm library)

Angular 20 library. Sources are compiled from src/app via symlink projects/enso-workflow-builder/src/lib../../../src/app.

The only supported publish path

cd /Users/trivenigogireddy/Work/workflow-builder   # REPO ROOT — not projects/, not dist/
nvm use 22

# 1) Bump version in projects/enso-workflow-builder/package.json (new number every release)
# 2) Publish (always rebuilds + verifies compiled .mjs, then publishes dist/)
npm run publish:lib
# npm run publish:lib -- --otp=123456

Then in the host (enso-suite):

npm install [email protected]
ls node_modules/enso-workflow-builder/fesm2022/   # must exist

Why hosts sometimes “don’t see changes”

| Mistake | Result on npm | | --- | --- | | npm publish inside projects/enso-workflow-builder | Tiny source tarball, no fesm2022/*.mjs (this was 0.1.9) | | Publish without rebuild / Node 18 build fail | New version string, old JS | | Reinstall same version | npm keeps the first tarball forever |

Guards now in place:

  • projects/.../package.json is private: true + prepublishOnly → cannot publish from projects/
  • npm run publish:lib always: Node check → ng build → strip private → assert fresh .mjs + UI markers + size → publish only dist/

Verify a published version

npm pack [email protected]
tar -tzf enso-workflow-builder-x.y.z.tgz | head
# must list package/fesm2022/enso-workflow-builder.mjs

Host docs

See docs/workflow-builder-ui-embed.md.