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

@equinor/roma-nx-plugin

v6.2.0

Published

This library was generated with [Nx](https://nx.dev).

Readme

roma

This library was generated with Nx.

Building

Run nx build roma to build the library.

Running unit tests

Run nx test roma to execute the unit tests via Jest.

CSP check

The serve and build executors run a static Content-Security-Policy check that warns when an app references an external resource that would be blocked in production by the workbench CSP. It scans first-party modules for external http(s)/ws(s) URLs used in:

  • import / dynamic import() / side-effect imports → script-src
  • fetch / WebSocket / EventSourceconnect-src
  • CSS url(...)img-src (or font-src for font files)
  • CSS @importstyle-src

Each URL's origin is compared against the relevant CSP directive (falling back to default-src). Violations are logged as warnings — the check never fails the build. Plain string-literal URLs (e.g. link hrefs) are intentionally ignored, since CSP fetch directives do not block them.

Source of truth

The CSP is the one defined in apps/workbench/public/staticwebapp.config.json. Because that file is not part of the published plugin, a snapshot is bundled at src/executors/utils/csp/data/generated-csp.json. Refresh it whenever the workbench CSP changes:

nx run roma:generate-csp

The check is disabled automatically (no warnings) if the bundled snapshot is missing or unparseable.