I have a setup where teams are publishing npm packages to Artifactory. Other teams consume these npm packages via a proxy set up in Nexus.
I had an issue where: - a user published a new npm package to Artifactory - a user tried to consume this package via Nexus and got the following error: npm ERR! No compatible version found: ui-dropdown@0.2.3 npm ERR! Valid install targets: npm ERR! 0.2.2, 0.2.1, 0.2.0, 0.1.8, 0.1.7, 0.1.6, 0.1.5, 0.1.4, 0.1.3, 0.1.2, 0.1.1, 0.1.0 - I logged into Artifactory and submitted the 'Recalculated Index' button - the user was able to consume the package Question: - Why does Artifactory not recalculate this index on the fly, especially after a new package has been published? - Is there any way to automate the recalculation of the index? I couldn't find anything in the UI. - Is there any documentation available for indexing in Artifactory? I couldn't find any. -- View this message in context: http://forums.jfrog.org/Artifactory-Npm-Index-tp7581079.html Sent from the Artifactory - Users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://pubads.g.doubleclick.net/gampad/clk?id=1444514421&iu=/41014381 _______________________________________________ Artifactory-users mailing list Artifactory-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/artifactory-users
