ENOENT

[cagedwisdom]

I know it's alpha, but here is an error I came across (tip of master).
A couple questions:
Re: Todo for basic bittorrent client as chrome app - Are you talking about a chrome extension? If so, why?
What kind of api do you have in mind for webtorrent-swarm? I assuming that's the bit that sorts out segmented file transfers.

$ npm start

> webtorrent@0.2.4 start /home/cagedwisdom/webtorrent
> npm run build && ./bin/start.js

> webtorrent@0.2.4 build /home/cagedwisdom/webtorrent
> npm run build-css && npm run build-js

> webtorrent@0.2.4 build-css /home/cagedwisdom/webtorrent
> stylus --use nib css/main.styl --compress --out chrome/ && ./bin/post-build.js

  compiled chrome/main.css

> webtorrent@0.2.4 build-js /home/cagedwisdom/webtorrent
> browserify --debug . > chrome/bundle.js


events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: spawn ENOENT
    at errnoException (child_process.js:988:11)
    at Process.ChildProcess._handle.onexit (child_process.js:779:34)
npm ERR! weird error 8
npm ERR! not ok code 0

[feross]

I'm fairly certain this issue is because the code currently assumes you have Chrome Canary for Mac installed and attempts to launch the chrome app in that browser. This is what I've been using to develop, but obviously we should figure out something better so others can contribute more easily. You can change the path here (https://github.com/feross/webtorrent/blob/master/bin/start.js#L5) to your chrome binary to get it working.

[feross]

See #39 for the answer to your "why" question.

[shyamsalimkumar]

Uhm...
Hi there... 👋
I changed the line you mentioned to var BIN = 'google-chrome' and this fires up Chrome alright, but it throws an Could not load extension from ''. Manifest file is missing or unreadable. alert message. I'm not sure where the Manifest file is, so some clues or pointers for resolving this problem would be helpful. Thanks in advance.

[feross]

@shyamsalimkumar What OS and OS version are you using? If you give me that info I can debug this.

[shyamsalimkumar]

Ubuntu 13.10 32bit... I presume that the Linux support has been added as I noticed #40 was merged, and it seemed to indicate that.

[deepak1556]

yup can confirm same error as @shyamsalimkumar on windows with chrome 33.0.1750.154 m. But i can load the app via chrome://extensions then it gave me a error first regarding socket api nt available then i had to change manifest to having sockets property instead of placing it in permissions. Then it worked :) but no idea abt y the cli is not picking up the same manifest.json.. @feross any clue?

{
  "manifest_version": 2,
  "name": "WebTorrent",
  "version": "0.1.0",
  "author": "Feross Aboukhadijeh",

  "app": {
    "background": {
      "scripts": ["bundle.js"]
    }
  },

  "description": "Simple, robust BitTorrent client for the browser",
  "icons": { "16": "calculator-16.png", "128": "calculator-128.png" },

  "sockets": {
        "tcp": {
          "connect": ""
        },
        "tcpServer": {
          "listen": ""
        },
        "udp": {
          "send": "",
          "bind": ""
        }
  },

  "permissions": [
    "storage",
    "unlimitedStorage",
    {
      "fileSystem": [
        "write",
        "retainEntries",
        "directory"
      ]
    },
    "http://*/*",
    "contextMenus"
  ],

  "offline_enabled": true
}

[feross]

Not sure why people are experiencing these errors. I'll investigate.

[rabidaudio]

Same on Arch. I thought at first that --load-and-launch-app might want the full path, but that wasn't the issue.