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

@rm98/polaris-polaris-nx

v0.5.3

Published

This library is a plugin for the [Nx](https://nx.dev) CLI. It is wrapped by the *Polaris CLI*.

Readme

Polaris Plugin for Nx CLI

This library is a plugin for the Nx CLI. It is wrapped by the Polaris CLI.

For more information, please have a look at the Polaris CLI documentation.

Running E2E Tests and Manual Testing

Run nx e2e polaris-nx-e2e to execute the E2E tests. This will generate a temporary workspace in the tmp subfolder of this workspace, which can also be used for manually testing the plugin.

Running the E2E tests in a JavaScript Debug Terminal in VS Code often makes the tests run into a timeout. Thus, it seems to be a better strategy to run a test command in the debugger. To set breakpoints inside polaris-nx, they must be set in the files in the dist/libs/polaris-nx directory. To set breakpoints inside a third-party library, they must be set in the files in the dist/libs/polaris-nx/node_modules directory.

If files without an extension should be included by a generator (e.g., Dockerfile), they must be explicitly added to the assets of the polaris-nx project in angular.json.

To test the Polaris CLI wrapper around the Nx plugin, please see the README of the Polaris CLI.