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

maersk-pool-partner

v1.9.0

Published

React app for Maersk Pool Partner

Readme

Insite digital website (frontend)

React app for Maersk Pool Partner

Setting up development environment

Adding environmental variables to the application

variables should be added in webpack.env.local.js for local environment purposes. Test/Stage/Production variables are defined as GitLab variable.

You can get them from CI/CD or k8s if you want to do that yourself or just ask your teammate. Add 'NPM_TOKEN' to system environmental variables.

To install packages use command:

yarn install --production=false

Development

For development use command (browsersync implemented):

yarn run dev

It sets up project on http://localhost:1234, changes in code doesn't require to reload page in browser.

Building production

To build project in production version use command:

npm run build

All output files will be saved in dist directory

Testing

Project is using Jest Tests. More info about how to write tests in React and Redux.

To run one pass of test execute command

npm run test

During development use test in watch mode which checks for changes and updates status immediately.

npm run test:watch

To update test snapshots execute:

npm run test:update

Icons

Project is using icomoon for generating font with embedded svg icons.

  • Generated fonts files are located in assets/fonts/mt-pool-partners
  • Styles for font are kept in styles/vendors/icomoon

In order to update this font you need to import json to icomoon located in styles/vendors/icomoon/selection.json. Remember to keep this file updated.

Keep your eye on the size of the icon inside font -> to tweak it chose edit / scale / fit to canvas feature. What we aim at is that all the icons inside the font feel like they are of the same size.

Remember to update path in variables.scss In our repository the correct path should be: /assets/fonts/mt-pool-partners

To use icon you need to add class icon with icon name like that:

<i class="icon-logo"></i>

After regenerating icons you need to be aware that paths will be different so you need to fix them by yourself.

Deployment

Requirements

to be able to deploy you need to install

Credentials

All credentials are stored in 1password

Manual test server deployment

change image tag to current day and hour when the deploy it was made - it helps to find which one is currently on test

IMAGE_TAG=manual-dd-mm-yyyy-hh-mm
BUILD_IMAGE="acrnoeupmtd.azurecr.io/poolpartner/mt.pp.frontend.img:$IMAGE_TAG"

build docker image and push to docker repository

docker login acrnoeupmtd.azurecr.io -u $MTD_ACR_LOGIN -p $MTD_ACR_PASSWORD
docker build --pull -t $MTD_ACR_BUILD_IMAGE .
docker push $MTD_ACR_BUILD_IMAGE

deploy docker image to server

helm upgrade mt-pool-partner-test helm\mt-pool-partner --namespace mt-test --install --set imageTag=$IMAGE_TAG,ingress.host=test.insitedigital.net