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/procosys-webapp-components

v6.1.6

Published

Library for sharing components and modules between Procosys MC webapp, Comm webapp and Echo.

Downloads

402

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

rtd-equinorrtd-equinorsopedsopedken.mellemken.mellem

Keywords

Readme

This library exists to share visual components as well as entire modules between the Procosys MC webapp, commissioning webapp and other Equinor solutions, such as Echo Infield.

These are the existing and planned modules:

  • Attachments
  • MCCR checklists
  • Tag OCR (pending major upgrade)
  • CPCL checklists (planned)
  • Punch (planned)
  • Commissioning Action log (planned)
  • Commissioning Tasks (not planned, but expected)

Most modules require your app, represented by an Azure App Registration, to have access to the relevant Procosys API. Please contact the Procosys team to obtain this access.

How to use this library:

  • Run "yarn" in the root of this repo
  • Run "yarn link"

To link to this library

  • Run "yarn start"
  • Run "yarn link @equinor/procosys-webapp-components" in the app you want to test the code in.

To unlink

  • Run "yarn unlink @equinor/procosys-webapp-components" in the app you tested the code in.

For info on how to contribute and publish changes to the package, please check out the guide in the Procosys Wiki Frontend section.

Installing the package

This package is published to npmjs.com under the @equinor scope, alongside the EDS packages (@equinor/eds-*) and other @equinor dependencies.

  1. Install the package:

    yarn add @equinor/procosys-webapp-components

    or

    npm install @equinor/procosys-webapp-components

No .npmrc or auth token is required for installing, since the package is public on npmjs.com.

Publishing

Publishing is automated via the 📦 Publish package GitHub Actions workflow (.github/workflows/publish.yml). On every push to main, the workflow builds the package and publishes it to npmjs.com only if the version in package.json has not already been published. This means routine commits to main won't fail when the version is unchanged.

To release a new version:

  1. Bump the version field in package.json.
  2. Merge to main. The workflow publishes the new version automatically.

Authentication (Trusted Publisher / OIDC)

Publishing uses npm's Trusted Publisher (OIDC) feature, so no npm token is required. The workflow authenticates tokenlessly via GitHub Actions OIDC (id-token: write permission). The package on npmjs.com must have this repository and the publish.yml workflow configured as a Trusted Publisher.