4 ms·

There's also this library: https://github.com/caolan/async https://github.com/caolan/async

• Sephr 14y ago
  That library uses callbacks and isn't really related other than the name. I don't think that the author googled async.js to see if the library name was already taken.
  • jonpacker 14y ago
    I think it's more likely he found it was not taken on npm so he took it. Async is, these days, one of the most popular libs on npm.
  • tlrobinson 14y ago
    https://github.com/caolan/async https://github.com/caolan/async: 3293 stars on Github https://github.com/eligrey/async.js https://github.com/eligrey/async.js: 15 stars on Github Sorry, you lost this one.
    • Sephr 14y ago
      Sorry, but what do stars have to do with it? That's like saying DuckDuckGo should be allowed to rename itself as Google if they become more popular than Google. https://github.com/caolan/async https://github.com/caolan/async had zero stars (i.e. didn't exist) back when I released async.js.
      • tlrobinson 14y ago
        I'm just saying you're going to have a hard time convincing everyone that your project is the "async" JavaScript library. I presume you don't plan on suing them for trademark infringement. It's annoying (it's happened to me too) but I don't think there's much you can do about it. Especially when the name is incredibly generic.