{"id":4696,"date":"2016-07-13T21:10:28","date_gmt":"2016-07-13T21:10:28","guid":{"rendered":"http:\/\/www.garysieling.com\/blog\/?p=4696"},"modified":"2016-07-13T21:10:28","modified_gmt":"2016-07-13T21:10:28","slug":"sonatype-nexus-clear-npm-cache","status":"publish","type":"post","link":"https:\/\/www.garysieling.com\/blog\/sonatype-nexus-clear-npm-cache\/","title":{"rendered":"Sonatype Nexus: clear npm cache"},"content":{"rendered":"

If you have a SonaType Nexus repository that combines multiple NPM targets (e.g. your own + the central NPM registry)\"\", you may find that you want to change the order of these.<\/p>\n

To do this, you can simply change the order in the Nexus UI:
\n\"\"<\/p>\n

However, for the change to actually take effect, you need to clear the cache for the repository group – this is the “Expire cache” option on the right click menu.<\/p>\n

Also note that you can test whether the change took effect by directly targeting the URL for the NPM repository \/ library you care about (e.g. http:\/\/garysieling.com:8081\/nexus\/content\/repositories\/npm-all\/my-library).<\/p>\n","protected":false},"excerpt":{"rendered":"

Fixing caching issues in SonaType Nexus<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[9],"tags":[362,382,393],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t