@axah/cache
Advanced tools
cache (in-memory and redis) utility for microservices at AXA Healthcare switzerland.
Install @axah/cache using the following command:
yarn add @axah/cache
When a PR is still open and you want to give it a try you can use a build created by Pika CI. Head to the Checks tab of your PR and select the Pika CI action where you find instructions on how to install the package built out of this PR.
Create a release on github and name the tag in the format vMAJOR.MINOR.PATCH and the github action in .github/workflows/publish.yml will take care of publishing the package to npm.
Note: As this technique currently updates the npm dist-tag latest to whatever release you create you should either not use this technique to cut a prerelease (i.e. using pattern vMAJOR.MINOR.PATCH-PRERELEASE.NUMBER) or a patch/minor version of an old major/minor OR fix the npm dist-tag afterwards using npm dist-tag @axah/cache@<latest version> latest
FAQs
Provides a cache either backed by RAM or redis
The npm package @axah/cache receives a total of 1,512 weekly downloads. As such, @axah/cache popularity was classified as popular.
We found that @axah/cache demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
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.
Security News
Snyk's use of malicious npm packages for research raises ethical concerns, highlighting risks in public deployment, data exfiltration, and unauthorized testing.
Research
Security News
Socket researchers found several malicious npm packages typosquatting Chalk and Chokidar, targeting Node.js developers with kill switches and data theft.
Security News
pnpm 10 blocks lifecycle scripts by default to improve security, addressing supply chain attack risks but sparking debate over compatibility and workflow changes.