search

GoogleChromeLabs / sw-toolbox

[Deprecated] A collection of service worker tools for offlining runtime requests
https://developers.google.com/web/tools/workbox/guides/migrations/migrate-from-sw
Apache License 2.0
3.62k stars 332 forks source link

install error #243

Open madneal opened 7 years ago

madneal commented 7 years ago

I have tried this demo at the beginning and encounter a error when execute npm install. Platform: win10 error info:

 Installing formidable@1.0.xplatform unsupported browser-sync@2.18.8 › chokidar@1.6.1 › fsevents@1.1.1 Package require os(darwin) not compatible with your platform(win32)
[fsevents@^1.0.0] optional install error: Package require os(darwin) not compatible with your platform(win32)
  ‼ tunneling socket could not be established, cause=connect ETIMEDOUT 180.168.41.175:80
  ‼ optipng pre-build test failed
  i compiling from source                                                                                                                                                                                                × RequestError : tunneling socket could not be established, cause=connect ETIMEDOUT 180.168.41.175:80
    at ClientRequest.<anonymous> (C:\Users\neal1\project\airhorn\node_modules\.5.7.1@got\index.js:74:21)
    at ClientRequest.g (events.js:291:16)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at ClientRequest.onError (C:\Users\neal1\project\airhorn\node_modules\.0.4.3@tunnel-agent\index.js:178:21)
    at ClientRequest.g (events.js:291:16)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at Socket.socketErrorListener (_http_client.js:310:9)
    at emitOne (events.js:96:13)
  ‼ tunneling socket could not be established, statusCode=400
  ‼ jpegtran pre-build test failed
  i compiling from source
  × RequestError: tunneling socket could not be established, statusCode=400
    at ClientRequest.<anonymous> (C:\Users\neal1\project\airhorn\node_modules\.5.7.1@got\index.js:74:21)
    at ClientRequest.g (events.js:291:16)
    at emitOne (events.js:96:13)
    at ClientRequest.emit (events.js:188:7)
    at ClientRequest.onConnect (C:\Users\neal1\project\airhorn\node_modules\.0.4.3@tunnel-agent\index.js:167:23)
    at ClientRequest.g (events.js:291:16)
    at emitThree (events.js:116:13)
    at ClientRequest.emit (events.js:194:7)
    at Socket.socketOnData (_http_client.js:395:11)
    at emitOne (events.js:96:13)

It seems that is have something with the package brower-sync.