Skip to content

History / Troubleshooting

Revisions

  • Update for current realities

    @iarna iarna committed Jul 17, 2018
    91ac7cf

  • add `UNABLE_TO_GET_ISSUER_CERT_LOCALLY` troubleshooting

    @kenany kenany committed Mar 24, 2017
    b00b523

  • add another instance of Kaspersky's SSL-intercepting

    @kenany kenany committed Mar 24, 2017
    9f96401

  • Updated Troubleshooting (markdown)

    @iarna iarna committed Feb 26, 2016
    369589f

  • defootgunned npm@3 upgrade path

    @othiym23 othiym23 committed Sep 21, 2015
    fa62f64

  • Add tip about using `-verbose` with `npm install`

    @nsarno nsarno committed Aug 14, 2015
    7ea5232

  • Updated Troubleshooting (markdown)

    @mrjcleaver mrjcleaver committed Aug 14, 2015
    578691a

  • Updated Troubleshooting (markdown)

    @mrjcleaver mrjcleaver committed Aug 14, 2015
    22ab1b9

  • npm config set prefix '${APPDATA}/npm' -g with single quotes causes the parameter to get set as "'${APPDATA}/npm'" (with double and single quotes) which causes npm to no longer function correctly (issues was occurring in Windows 10). This command probably doesn't require quotes at all but I haven't tested with all versions of Windows.

    @mattgaspar mattgaspar committed Aug 10, 2015
    7ce98ea

  • Updated Troubleshooting (markdown)

    @felixrieseberg felixrieseberg committed Jun 29, 2015
    a1acbbb

  • Updated Troubleshooting (markdown)

    @felixrieseberg felixrieseberg committed Jun 29, 2015
    4f5abc9

  • Updated Troubleshooting (markdown)

    @iarna iarna committed Jun 28, 2015
    393887a

  • Update the note on configuring .npmrc per issue #8717

    @busches busches committed Jun 28, 2015
    8134917

  • Fixed upgrading windows instructions (especially option 3). used env variables because NodeJS is now default to 64bit on 64bit machines.

    Robert Baker committed May 22, 2015
    58ac77b

  • Updated Troubleshooting (markdown)

    @smikes smikes committed May 20, 2015
    ab91b3a

  • Using option 1,2 or 3 makes a difference for where the npmrc file should be placed.

    @willemmulder willemmulder committed Apr 1, 2015
    737f97f

  • use `npm@latest` in updating on Windows, option 3

    @smikes smikes committed Mar 20, 2015
    00f54f6

  • got rid of bad tip

    @othiym23 othiym23 committed Mar 18, 2015
    10b4902

  • fromagerie

    @othiym23 othiym23 committed Mar 18, 2015
    beb4228

  • updated shrinkwrap issue

    @othiym23 othiym23 committed Mar 18, 2015
    6f5d452

  • added solution to long path issues

    @othiym23 othiym23 committed Mar 18, 2015
    df9ad8f

  • Add note re SSL-intercepting proxy

    @smikes smikes committed Feb 25, 2015
    5df9b24

  • Add notes and link to source issue for npm-login-errors

    @smikes smikes committed Feb 24, 2015
    0b264a5

  • Add note about `npm login` errors

    @smikes smikes committed Feb 5, 2015
    e2b613c

  • update links to proxy configs

    @kenany kenany committed Jan 23, 2015
    5554451

  • need to follow redirect (or change to npmjs.com)

    @smikes smikes committed Jan 8, 2015
    531e84b

  • Fixes issue to issues in the two urls

    @faiq faiq committed Jan 1, 2015
    db365e7

  • ops, removed the Users/ path

    @maxgalbu maxgalbu committed Dec 18, 2014
    53fac8f

  • left my windows username there!

    @maxgalbu maxgalbu committed Dec 18, 2014
    a430ee7

  • the npmrc copy is obligatory after installing the new npm

    @maxgalbu maxgalbu committed Dec 18, 2014
    c1a4672