Invalid asm.js: Expected function name

[yuri-karadzhov]

What version of this package are you using?
webtorrent@0.108.1

What operating system, Node.js, and npm version?
MacOS Catalina 10.15.4
Node.js v12.16.1
npm 6.13.4

What happened?
Some (but not all) torrent links (that work with instant.io) does not work with basic example given a warning in console Invalid asm.js: Expected function name. Seems like an old issue with minification #281 and #1252

What did you expect to happen?
I would expect all magnet links will work the same way they do in instant.io

[alxhotel]

Hi @yuri-karadzhov, thanks for the feedback :)

Can you give some examples of working and not working magnet links ?

[yuri-karadzhov]

Well I tried some random stuff from well known torrents vs sintel link from example. I guess the problem is with minification of webtorrent.min.js

[yuri-karadzhov]

@alxhotel I spot the difference, instant.io adds &tr=wss%3A%2F%2Ftracker.btorrent.xyz&tr=wss%3A%2F%2Ftracker.fastcast.nz&tr=wss%3A%2F%2Ftracker.openwebtorrent.com to the end of the link. I tried it and it starts working. Am I missing some part of API that searches for additional torrents or this list is known and hardcoded?

[XayOn]

That's a common feature on most bittorrent clients, adding trackers.
You could use magnet-uri to parse the magnet link and add the trackers ( wss://tracker.bttorrent.xyz, wss:tracker.fastcast.nz and wss:tracker.openwebtorrent.com ).

I use something like this:

import magnet from 'magnet-uri';
let torrent_origin = "magnet:...."
let decoded = magnet.decode(torrent_origin)
decoded['tr'].push('wss://tracker.openwebtorrent.com')
let torrent_origin = magnet.encode(decoded);

If you use webtorrent-desktop, you could also grab the magnet link from it, as it adds the trackers automatically.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[feross]

Invalid asm.js: Expected function name is a harmless warning that Firefox sometimes emits. See: #1252

The right place to fix is in the upstream babel-minify project