@exponent/react-native-navigator is not on npm about ex-navigator HOT 7 CLOSED

@pietropizzi Thanks for the follow-up. To workaround the issue you could try installing the module directly from GitHub with npm i exponentjs/ex-navigator#5a4191e9b, for example. We do a lot of updates and tend not to use Git tags / GH releases, but do try to mention in the commit titles when there is a new npm version, so you could adjust the Git commit hash in the package.json entry accordingly.

from ex-navigator.

@ide thanks. I was able to install it with npm install --registry=https://registry.npmjs.org so going straight to the public registry.

from ex-navigator.

It's publicly available here: https://www.npmjs.com/package/@exponent/react-native-navigator and we use in in our package.json like

  "dependencies": {
    "@exponent/react-native-navigator": "^0.2.4",

from ex-navigator.

Thanks for the quick response. It's interesting that it doesn't work for me. Which version of npm are you using? I am trying it on v2.14.2.

Also when you use the search on npm like so: https://www.npmjs.com/search?q=react-native-navigator your package does not come up.

from ex-navigator.

I'm on npm 2.14.8 though it has been working for awhile.

from ex-navigator.

Ok so I have found the issue. We are using our own private registry build with Sinopia. When running npm install it first goes to our server and if it can't find it there it goes to the public one. Apparently there is some bug in that pipeline when the package is scoped.

Also for the fact that you can not find scoped packages on npm, here is the issue: npm/npm#8453

from ex-navigator.

Great, that's even better!

from ex-navigator.