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

create-thingworx-widget2

v1.0.4

Published

Scaffold a ThingWorx custom widget project — like npm create vite@latest but for ThingWorx.

Readme

create-thingworx-widget

Scaffold a production-ready ThingWorx custom widget project in seconds — just like npm create vite@latest.

Usage

npm create thingworx-widget2@latest
# or
npx create-thingworx-widget2

The CLI will ask you a few questions (widget name, description, ThingWorx server, chart library, etc.) and generate a complete project folder.

What gets generated

MyWidget/
├── src/
│   ├── MyWidget.ide.js        ← Composer (IDE) behaviour & property definitions
│   ├── MyWidget.runtime.js    ← Mashup runtime rendering & data handling
│   ├── MyWidget.ide.css       ← Composer styles
│   ├── MyWidget.runtime.css   ← Runtime styles
│   └── echarts.min.js         ← (placeholder if ECharts selected)
├── build/                     ← Gulp output (gitignored)
├── zip/                       ← Extension .zip ready for TWX import
├── metadata.xml               ← ThingWorx extension manifest
├── gulpfile.js                ← Build pipeline (clean → copy → babel → minify → zip)
├── package.json
├── .gitignore
└── README.md

Generated npm scripts

| Command | Description | | -------------------------- | ------------------------------------------- | | npm run build | Dev build (unminified) → zip/ | | npm run buildProduction | Production build (concat + minify) → zip/ | | npm run upload | Dev build + upload to ThingWorx | | npm run uploadProduction | Production build + upload to ThingWorx |

Publishing to npm

npm login
npm publish --access public

Once published, anyone can run:

npm create thingworx-widget@latest

Local development / testing

# Inside this package folder
node bin/create-thingworx-widget.js

# Or link globally
npm link
create-thingworx-widget

How the build pipeline works

The Gulp pipeline (gulpfile.js) mirrors the proven pattern from the LinearGradientWidget:

  1. cleanBuildDir — wipes build/, zip/, lib/
  2. copy — copies src/**build/ui/<PackageName>/ and metadata.xmlbuild/
  3. prepareBuild
    • Babel transpiles all JS (removes ES module import/export for TWX compatibility)
    • In --p (production) mode: reads metadata.xml, groups JS files by IDE/Runtime, concatenates + minifies with Terser, updates metadata.xml references
    • Zips build/zip/<PackageName>-dev|min-<version>.zip
  4. upload (optional) — POSTs the zip to ThingWorx via the Extension Package Uploader servlet