deprecated node-uuid@1.4.7: use uuid module instead

Issue details

PS C:\windows\system32> npm --version 3.10.9 PS C:\windows\system32> node --version v6.9.2 PS C:\windows\system32> npm install -g browser-sync npm WARN deprecated node-uuid@1.4.7: use uuid module instead C:\Users\sahin_000\AppData\Roaming\npm\browser-sync -> C:\Users\sahin_000\AppData\Roaming\npm\node_modules\browser-sync
bin\browser-sync.js C:\Users\sahin_000\AppData\Roaming\npm -- browser-sync@2.18.5 – localtunnel@1.8.2 -- request@2.78.0 – http-signature@1.1.1 -- sshpk@1.10.1 +-- bcrypt-pbkdf@1.0.0 +-- ecc-jsbn@0.1.1 +-- jodid25519@1.0.2 +-- jsbn@0.1.0 – tweetnacl@0.14.5

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\browser-sync\node_modules\chokidar\node_mo dules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.0.15: wanted {“os”:“darwin”,“arch”:“an y”} (current: {“os”:“win32”,“arch”:“x64”})

PS C:\windows\system32> browser-sync --version browser-sync : The term ‘browser-sync’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. At line:1 char:1

• browser-sync --version

•   + CategoryInfo          : ObjectNotFound: (browser-sync:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException
  
  
  

Steps to reproduce/test case

I installed node through msi. Checked the version and it works.

Please specify which version of Browsersync, node and npm you’re running

• Browsersync [ Cannot install ]
• Node [ 6.9.2 ]
• Npm [ 3.10.9 ]

Affected platforms

• linux
• [X ] windows
• OS X
• freebsd
• solaris
• other (please specify which)

Browsersync use-case

• API
• Gulp
• Grunt
• CLI

If CLI, please paste the entire command below

{cli command here}

for all other use-cases, (gulp, grunt etc), please show us exactly how you’re using Browsersync

{Browsersync init code here}

[Bersam]

this is still happening, seems it is because of localtunnel, here’s on going issue on localtunnel. https://github.com/localtunnel/localtunnel/issues/162

[DanielRuf]

The localtunnel dependenc is on 1.8.2, the fix is in localtunnel 1.8.3 as localtunnel as request as dependency. So this issue is still not fixed.