Shane Bryan

I am also hitting this same error, also behind a firewall but with working proxy settings for npm (meaning I have no problems installing other modules from the standard registry)....

OK, so I did the right thing, and yet, it behaves as if it still can't find sauce-connect and tries to download it again... meaning it still does this: ```...

> have you tried installing sauce-connect-launcher and wct-sauce directly and not via web-component-tester? Yes. sauce-connect-launcher does not complain... installs fine, but does not attempt to build or fetch the native...

It would be even nicer if web-component-tester did not **require** wct-sauce :/ Seems odd that it is required to me, especially since it _is_ a plug-in. That's a feature request...