This repository has been archived by the owner. It is now read-only.

Oppskriftet ’Kom igang’ her: "https://github.com/navikt/nav-frontend-moduler" feiler #18867

Closed
Y130311-NAV opened this Issue Oct 17, 2017 · 1 comment

Comments

Projects
None yet
3 participants
@Y130311-NAV

Y130311-NAV commented Oct 17, 2017

I'm opening this issue because:

  • npm is crashing.
  • npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?


npm install gir feilmelding: Her er loggen fra Windows command vinduet (jeg fant ikke en måte å overføre npm-debug.log filen uten å først måtte dra hjem til privat PC):

C:\Users\Y130311\Projects>cd nav-frontend-moduler

C:\Users\Y130311\Projects\nav-frontend-moduler>npm install

npm ERR! registry error parsing json

npm ERR! registry error parsing json

npm WARN deprecated babel-preset-es2015@6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

npm ERR! Windows_NT 10.0.14393

npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"

npm ERR! node v6.11.3

npm ERR! npm v3.10.10

npm ERR! Unexpected token < in JSON at position 0

npm ERR!

npm ERR!

npm ERR! <title>404 Not Found</title>

npm ERR!

npm ERR!

Not Found

npm ERR!

The requested URL /nexus/content/groups/npm-all/@storybook/react was not found on this server.

npm ERR!


npm ERR!

Apache/2.2.15 (Red Hat) Server at maven.adeo.no Port 80

npm ERR!

npm ERR!

npm ERR!

npm ERR! If you need help, you may report this error at:

npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:

npm ERR! C:\Users\Y130311\Projects\nav-frontend-moduler\npm-debug.log

C:\Users\Y130311\Projects\nav-frontend-moduler>npm config set @Hypnosphi:registry http://a34apvl062.devillo.no:8082/repository/npm-all/

C:\Users\Y130311\Projects\nav-frontend-moduler>npm config set @types:registry http://a34apvl062.devillo.no:8082/repository/npm-all/

C:\Users\Y130311\Projects\nav-frontend-moduler>npm config set @storybook:registry http://a34apvl062.devillo.no:8082/repository/npm-all/

C:\Users\Y130311\Projects\nav-frontend-moduler>npm install

npm WARN deprecated babel-preset-es2015@6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

npm WARN deprecated babel-preset-es2016@6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

npm ERR! fetch failed http://maven.adeo.no/nexus/content/groups/npm-all/react-icons/-/react-icons-2.2.7.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404

npm ERR! fetch failed http://maven.adeo.no/nexus/content/groups/npm-all/react-icons/-/react-icons-2.2.7.tgz

npm WARN retry will retry, error on last attempt: Error: fetch failed with status code 404

npm ERR! fetch failed http://maven.adeo.no/nexus/content/groups/npm-all/react-icons/-/react-icons-2.2.7.tgz

npm ERR! Windows_NT 10.0.14393

npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install"

npm ERR! node v6.11.3

npm ERR! npm v3.10.10

npm ERR! fetch failed with status code 404

npm ERR!

npm ERR! If you need help, you may report this error at:

npm ERR! https://github.com/npm/npm/issues

npm ERR! Please include the following file with any support request:

npm ERR! C:\Users\Y130311\Projects\nav-frontend-moduler\npm-debug.log

C:\Users\Y130311\Projects\nav-frontend-moduler>

MVH,

Sato *: satilmis.yayla@nav.no // IM: sip:satilmis.yayla@nav.no // ): +47 91 307 386


How can the CLI team reproduce the problem?


Nav desktop -> start VM Ware View Client (ny) -> Windows 10 v 1.0 -> start git GUI -> clone repositoriet https://github.com/navikt/nav-frontend-moduler til lokaldisk i den virtuelle PC'en her C:\Users<username>\Projects\nav-frontend-moduler -> søk i star meny for cmd kommando og kjør den -> kjør kommandoene i "kom i gang" oppskriftet i oppgitt rekke i filen readme.md eller lenger ned på forsiden av github.com adressen ovenfor.

supporting information:

  • npm -v prints:
  • node -v prints:
  • npm config get registry prints:
  • Windows, OS X/macOS, or Linux?:
  • Network issues:
    • Geographic location where npm was run:
    • I use a proxy to connect to the npm registry.
    • I use a proxy to connect to the web.
    • I use a proxy when downloading Git repos.
    • I access the npm registry via a VPN
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:
    • I develop using Vagrant on Windows.
    • I develop using Vagrant on OS X or Linux.
    • I develop / deploy using Docker.
    • I deploy to a PaaS (Triton, Heroku).

@KenanY KenanY added the support label Oct 17, 2017

@npm-robot

This comment has been minimized.

Show comment
Hide comment
@npm-robot

npm-robot Oct 27, 2017

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

npm-robot commented Oct 27, 2017

We're closing this support issue as it has gone three days without activity. The npm CLI team itself does not provide support via this issue tracker, but we are happy when users help each other here. In our experience once a support issue goes dormant it's unlikely to get further activity. If you're still having problems, you may be better served by joining WeAllJS and asking your question in its #npm channel. The npm CLI team is all present there, but there are also lots of other folks who can help you too.

For more information about our new issue aging policies and why we've instituted them please see our blog post.

@npm-robot npm-robot closed this Oct 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.