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 🙏

© 2025 – Pkg Stats / Ryan Hefner

webui2

v0.0.0

Published

Spectrum Web UI Build Dependencies

Readme

Sample Deployable Web UI View

Note: readme.md best viewed with a markdown preview app such as Chrome's Markdown Preview extension or the idea-markdown plugin for IntelliJ.

Building

Build war file: mvn clean install

Performs the following actions:

  1. Downloads all node modules required for building the web app.
  2. Downloads the javascript libraries used by the web management console (including the Spectrum web sdk).
  3. Performs a build using grunt.
  4. Packages the results in a war file in the target directory.
  5. If the maven development profile is active, the newly created war file is automatically copied to the deployment folder of the development Spectrum distribution:      cdqp/trunk/development/platform/server/container/dist/target/spectrum-server-distribution/server/app/deploy/

Build web app: grunt or grunt build:prod

The production build script utilized by mvn clean install. It assumes all artifacts/dependencies have been downloaded.
This will run a build that includes all the goodies (linting, minification, testing, etc.). All artifacts will be placed in the dist directory. It does not create the war file (use maven for this).

Developing

Development build: grunt build:dev

Runs a build that excludes minification. This allows debugging of non-minified code.

All artifacts will be placed in the dist directory and also copied to the "live" deployment location within the development Spectrum distribution:      cdqp/trunk/development/platform/server/container/dist/target/spectrum-server-distribution/server/app/tmp/web/iedeployableview.war/webapp This allows for the contents to be hot-deployed to a running Spectrum server.

In addition, a watch task will continue to run in the background. Whenever any changes to a source file (js, html, css, json translations) are detected, the associated file will be auto-deployed to the running Spectrum server. Simply refresh an existing browser connection to load/view the changes.

Testing

Run Karma: grunt test

This will fire up the Karma unit test runner and open a new Chrome window. Karma automatically detects changes to JavaScript files and executes all unit tests found in the project. The results of the tests will be outputted in the command window.

To debug unit tests, click the Debug button in the browser window to debug directly in Chrome. To use IntelliJ to debug, create a JavaScript Debug configuration and point it to http://localhost:9876. Alternatively, install the IntelliJ Karma plugin to run/debug Karma directly from IntelliJ.