I’m looking for a way to force NPM to update the cached README for my package. Despite republishing several times, the information displayed is still outdated. Does anyone have a step-by-step method to manually trigger this cache refresh so that the new README content becomes visible? Any insights or alternative approaches to ensure that NPM reflects the current description would be greatly appreciated.
i had to bump the version in my package and re-publish. no direct manual refresh yet so it worked for me as a workaround. might take a bit to update though
After working through this issue for a while, I found that there isn’t a direct method to simply refresh the README cache on NPM. The only working approach is to update the package by increasing its version number and republishing it. This automatically prompts NPM to rebuild the cached README, which is the only reliable method based on my experience. While it might not be the most ideal or convenient solution, at this time no alternate means exists to manually trigger a cache refresh.
I experienced this issue when working on a similar package update. I was frustrated at first because the changes I made weren’t reflected immediately. After some trial and error, I resorted to increasing the version number, which eventually forced the cache to refresh. Although it might seem like an unnecessary workaround, it has been the only solution that consistently activates an update on the cached README. In the meantime, checking for propagation delays and allowing some time for the changes to take effect can also help.