npm package takes longer to be actually available even after the publishing is complete, it appears that npm keep scanning the package for security purpose or some sort.
one workaround is to retry the npm install, otherwise we'll have to comment out this step in order to pass the CI workflow.
npm package takes longer to be actually available even after the publishing is complete, it appears that npm keep scanning the package for security purpose or some sort.
one workaround is to retry the npm install, otherwise we'll have to comment out this step in order to pass the CI workflow.