# Npm install of JavaScript SDK fails

**URL:** <https://forums.rocket.chat/t/npm-install-of-javascript-sdk-fails/746>\
**Category:** Community Support\
**Created:** [May 9, 2018, 11:48pm UTC](https://forums.rocket.chat/t/npm-install-of-javascript-sdk-fails/746 "2018-05-09T23:48:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![arthur.temporim](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/arthur.temporim/32/266_2.png) [@arthur.temporim](https://forums.rocket.chat/u/arthur.temporim)\
**Post date:** [May 9, 2018, 11:48pm UTC](https://forums.rocket.chat/t/npm-install-of-javascript-sdk-fails/746/1 "2018-05-09T23:48:31Z")

</div>

Using npm in version`6.0.0`, when trying to install [Rocketchat JS SDK](https://www.npmjs.com/package/@rocket.chat/sdk) I have this error:

```auto
npm install @rocket.chat/sdk --save
+ @rocket.chat/sdk@0.2.1
updated 1 package in 3.149s
[!] 40 vulnerabilities found [534 packages audited]
    Severity: 22 low | 4 moderate | 14 high
    Run `npm audit` for more detail

```

After running `npm audit` and update the suggested packages still having this problem:

```auto
> node ./bin/install.js

husky
setting up Git hooks
done

> node postinstall

added 663 packages from 1196 contributors in 7.71s
[!] 2 vulnerabilities found [3025 packages audited]
    Severity: 2 low
    Run `npm audit` for more detail

```

So the solution was just to downgrade the npm version to `5.6.0` and everything works fine. This [link](https://blog.npmjs.org/post/173719309445/npm-audit-identify-and-fix-insecure) have an explanation.

---

<div class="post-metadata">

**Author:** ![aaron.ogle](https://sea1.discourse-cdn.com/flex021/user_avatar/forums.rocket.chat/aaron.ogle/32/15_2.png) [@aaron.ogle](https://forums.rocket.chat/u/aaron.ogle)\
**Post date:** [May 31, 2018, 7:30pm UTC](https://forums.rocket.chat/t/npm-install-of-javascript-sdk-fails/746/2 "2018-05-31T19:30:19Z")

</div>

Is that actually an error? I’ve seen those but things have installed and worked fine anyways. I think its just one of those things you ignore unless its actually not working after showing that message.