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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@axa-ch/pod-ice-kpv-summenmeldung

v1.2.6

Published

KPV Summenmeldung MVP

Downloads

2

Vulnerabilities

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

Links

Git

Maintainers

gianlucaguarinigianlucaguarinivalentin-haslervalentin-haslermarek.lacomarek.lacodomirsdomirsaxa-ch-useraxa-ch-usermatthias.zuerchermatthias.zuercherselinagahlingerselinagahlinger

Keywords

Readme

App KPV Summenmeldung

Dependencies installieren:

npm ci

Entwicklung:

npm start

Release:

npm run build:ci

Das Resultat ist das Directory build. Darin befinden sich alle statischen asssets (html, js, css...) für das Deployment.

Test des Releases:

npm run serve:app

Installing and Using Cypress for automated End-2-End Testing

In the open internet Cypress can be installed with npm i -D cypress.
The post install step of the cypress package tries to download the Cypress application (a binary). This download is blocked by the AXA proxy.

For this reason we have to install Cypress with some more ceremony:

  • Download the binary manually here: https://download.cypress.io/desktop
    (the McAfee Web Gateway took 10 min to check the file in my case)
  • Copy the file cypress.zip to C:\eplatform\tools\Cypress (the directory mus then contain the cypress.zip)
  • run in Windows CMD: set CYPRESS_INSTALL_BINARY=C:\eplatform\tools\Cypress\cypress.zip && npm i cypress --no-save
    (alternatively you can run npm run cypress:install)

The flag --no-save prevents the package to be added to the package.json and package-lock.json. This is not a good practice, but this enables new developer inside AXA to clone the project and successfully run npm install.
The drawback here is that a npm install will remove cypress again ... so you have to re-install it after every npm install.

Running Cypress for Development:

npm start
npm run cypress:open:local

Cypress single run on local machine:

npm start
npm run cypress:run:local

Cypress single run for continuous integration against DEV:

npm run cypress:ci:dev

POD PodIceKpvSummenmeldung

This is a Micro Frontend deployable on the AXA.ch WebHub.

Scripts

To install the pod locally: npm install @axa-ch/pod-ice-kpv-summenmeldung

DEV commands

  • npm start start local DEV environment
  • npm run build to trigger a ESM build needed for Midgard
  • npm run test to run local tests
  • npm run release to execute a release to NPM (VERY IMPORTANT: Read How To Release on this document).

How to release

  1. update package.json in the "version": "x.x.x" field. Please follow semver best practices

  2. run npm run release

  3. commit to develop, add git tag containg the same version as in step 1 and push

  4. Execute jenkins jobs (build & deploy and if all good: promote) with the version added in point 1

Worth a read