We are using the same version and experience exactly the same issue . The issue is happening all the time. In fact the only way to update the npm group will be to Invalidate the cache for the global nom group.
pavel1
(Pavel Pavlov)
2
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Npm group repo requires cache invalidation to see package in private repo | 3 | 3819 | October 18, 2019 | |
| NPM Update AND Install Issues | 7 | 4243 | January 3, 2023 | |
| NPM packages are not updated | 1 | 736 | November 22, 2022 | |
| Pushing to Nexus Group From Jenkins Pipeline | 0 | 920 | September 1, 2022 | |
| Cache issue with NuGet publish and Nexus groups | 0 | 252 | June 23, 2024 |