Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

@axa-ch/alt-alt-pod-test

Package Overview
Dependencies
Maintainers
48
Versions
2
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@axa-ch/alt-alt-pod-test

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

  • 0.0.1
  • unpublished
  • latest
  • Source
  • npm
  • Socket score

Version published
Maintainers
48
Created
Source

POD AltPodTest

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

Scripts

To install the pod locally: npm install @axa-ch/alt-pod-test

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

FAQs

Package last updated on 28 Jan 2022

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc