Nexus as NPM proxy repository display old packages

[Doron Haskel]

Hi 

I'm using Nexus for 3rd parties NPM content and I can see that some packages doesn't include updated version list.

for example "npm install lod...@4.5.1" return error that "No compatible version found:" while using directly registry.npmjs.org this package exists.

Thanks

Doron

[Rich Seddon]

What nexus version are you using?

Rich

--
You received this message because you are subscribed to the Google Groups "Nexus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nexus-users...@glists.sonatype.com.
To post to this group, send email to nexus...@glists.sonatype.com.
To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/24f7e07d-6912-405a-ad63-cb0b0832e2d5%40glists.sonatype.com.
For more options, visit https://groups.google.com/a/glists.sonatype.com/d/optout.

[Doron Haskel]

Sonatype Nexus™ Professional Edition, Version: 2.11.4-01

[Rich Seddon]

I'll need to get diagnostic information to be able to help.

Go to "administration/support tools/support zip" in the UI, and generate a support zip.  Then attach it to a ticket at https://support.sonatype.com, or email it to sup...@sonatype.com.

Rich

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/81cf431b-b483-4b27-94f0-2a1703787b12%40glists.sonatype.com.

[Christian Theilemann]

Hi,

same problem here,

this happened to me multiple times with the package "babel-register" which itself and it's dependencies are upgraded quite often.

It seems if a new version is published on public npm, it becomes in the internal registry only available after a few hours (caching issues?).

This led multiple times to problems with "babel-register" since some of it's transitive dependencies could not be found during installation and I get in npm errors like that:

00:03:37.265 INFO: npm ERR! node v0.12.4
00:03:37.265 INFO: npm ERR! npm  v2.10.1
00:03:37.265 INFO: npm ERR! code ETARGET
00:03:37.265 INFO: 
00:03:37.265 INFO: npm ERR! notarget No compatible version found: babel-code-frame@'>=6.7.2 <7.0.0'
00:03:37.265 INFO: npm ERR! notarget Valid install targets:
00:03:37.265 INFO: npm ERR! notarget ["6.0.0","6.0.2","6.0.12","6.0.14","6.0.15","6.1.4","6.1.5","6.1.6","6.1.7","6.1.8","6.1.9","6.1.10","6.1.11","6.1.12","6.1.13","6.1.14","6.1.15","6.1.16","6.1.17","6.1.18","6.2.4","6.3.13","6.5.0","6.5.0-1","6.6.0","6.6.5"]
00:03:37.265 INFO: npm ERR! notarget 
00:03:37.265 INFO: npm ERR! notarget This is most likely not a problem with npm itself.
00:03:37.265 INFO: npm ERR! notarget In most cases you or one of your dependencies are requesting
00:03:37.265 INFO: npm ERR! notarget a package version that doesn't exist.
00:03:37.265 INFO: npm ERR! notarget 
00:03:37.265 INFO: npm ERR! notarget It was specified as a dependency of 'babel-core'
00:03:37.265 INFO: npm ERR! notarget 

I unfortunately cannot get you easily diagnostic information, but I'm optimistic you can reproduce the issue by publishing a new version of a package on public npm and then try to install it immediately via private nexus proxy.

Best Regards Christian

[Peter Lynch]

On Thu, Mar 10, 2016 at 7:31 PM, Christian Theilemann <c.thei...@gmail.com> wrote:

Hi,

same problem here,

Nexus npm proxy repositories use the field Item Max Age to determine when to look for updates on the remote.

If the age has not yet expired for a dependent package, then you can force expire this by right-clicking the npm proxy repository in the repository list and selecting Expire Cache.

 

To view this discussion on the web visit https://groups.google.com/a/glists.sonatype.com/d/msgid/nexus-users/c356ccbd-ba3d-44d1-b271-2a215d84a49a%40glists.sonatype.com.

[Domenic Figliomeni]

Hi,

I had a similar issue but it was with the private repo.  I published an artifact (0.1.0) and it came up in the Nexus UI under my repo/components.  I incremented the version in package.json (0.2.0) and executed npm publish again.  In the Nexus Web UI, it looks like a separate component, there are now 2 entries with the same name under the components view.  Also, when I do an npm search for the component, npm reports 0.1.0 incorrectly as the latest version.  Does anyone else have the same issue?  I am using Nexus v 3.0.1-01.  Perhaps somebody can point me to another thread for this type of issue.

Thanks in advance :)