POD PodWebhubIframe
This is a Micro Frontend deployable on the AXA.ch WebHub.
Scripts
To install the pod locally: npm install @axa-ch/pod-webhub-iframe
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
-
update package.json in the
"version": "x.x.x"
field. Please follow semver best practices -
run
npm run release
-
commit to develop, add git tag containg the same version as in step 1 and push
-
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:
-
update package.json in the
"version": "x.x.x"
field (if you want). Please follow semver best practices -
run
npm run alt-release
-
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