Use the official local nodejs package.

[Varun-garg]

No description provided.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[Varun-garg]

I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[Pringels]

@Varun-garg This merge broke all our tests :( Can you please provide some context as to why this pull request was necessary?

[Varun-garg]

Hey @Pringels I just ran samples in this repo after upgrading the version and tests seemed to have run fine. We upgraded this repo because there were some cases where browserstacktunnel-wrapper was not able to properly download the BrowserStack Local binaries. Could you provide the logs so we can debug further?

[Pringels]

@Varun-garg the log simply indicates that Browserstack was unable to connect to our CI agents. (connection refused) I didn't spend much time investigating as I had an urgent release, so I just rolled back to 1.4. I will investigate further next week and get back to you.

[csvn]

@Pringels I think your CI broke due to either #155 or #156. I'm planning a PR to fix both as soon as I can.

Ping @Varun-garg