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-webhub-dtidemo

v0.0.0

Published

Micro-Frontend for https://axa.ch/

Downloads

2

Vulnerabilities

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

Links

Git

Maintainers

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

Keywords

Readme

POD PodWebhubDtidemo

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

Scripts

To install the pod locally: npm install @axa-ch/pod-webhub-dtidemo

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).
  • npm run alt-release to execute an alternative pod release to npm (VERY IMPORTANT: Read How To Release an alternative pod in 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) with the version added in point 1

How to release an alternative pod

It's possible (but optional) to create an alternative pod besides your actual pod. This alternative pod can be used for some assessments or testing session. An alternative pod can only be deployed to DEV and ACC. There is an extra script for alternative pod releases: alt-release If you execute this script it will change your pod name to alt-pod-your-pod-name, publish a version to npm and after publishing it will change the pod name back to the previous. The pod version will not change unless you change it manually.

For releasing an alternative pod follow these steps:

  1. update package.json in the "version": "x.x.x" field (if you want). Please follow semver best practices

  2. run npm run alt-release

  3. Execute jenkins jobs (build & deploy) with the version added in point 1

Worth a read

First release of your pod

While you create your pod you will be asked if it's OK to publish a first vesion of your pod to npm. If you choose "n" you have to execute the following script (only for your first pod version): npm run first-ever-release

For a first release of an alternative pod you have to execute the following script (only for your first pod version): npm run first-ever-alt-release