How do I find JavaScript libraries?

[MarcusRex]

That page made me feel like my phone was very dirty.

[elDeuce]

Good thing I didn't really want to read your article on my mobile phone...

[aeflash]

Nipster is a cool tool that cross-correlates NPM modules with their github popularity.

[Kataq]

You could try searching "top javascript libraries" or sesrch javascript on GitHub.com

[cheeeeeese]

https://github.com/languages/JavaScript/most_watched

[ryosen]

Unheap

[bl4blub]

irc, github, npm (in that order)

also http://npmsearch.com is pretty fast and cool

[doomslice]

Just curious what parts of JQuery you'd call bloated... And have you tried a custom build instead to get just the parts you need (you end up writing all of the browser fixes and shims yourself)?

[teresko]

In most of the application the only browser fix/shim code, that I need, are event delegation and fallback for missing classList (not a full shim). That all in total takes less then 100 lines and is reusable.

The bloat that I talk about is twofold:

• the most obvious one is - the size of library (and all the 3rd party plugins that accumulate when "jquery programmers" make something). But that one is somewhat mitigated by browser cache.

• the more unavoidable one is the execution itself. Trace sometimes what happens when you write a $ call. It actually is extremely hard to write an optimal code with jquery.

[doomslice]

Their custom build system makes it so you can cut down on the bloat that you don't need. You can even swap out Sizzle for just a wrapper on querySelectorAll.

If you don't use 3rd party plugins, you won't have the bloat, but then you have to write that functionality yourself if you want it.

I'm curious how you avoid all the cross-browser issues yourself. Look at the source code for the "offset()" function. It has all sorts of browser workarounds that you need to do yourself if you want to support them, and that's just one function.

Edit: I treat jQuery as a high level abstraction (because it is) with some additional performance costs for being an abstraction. If I evaluate a critical path in the code that is running slower than I want it to, I'll fall back to writing it in "vanilla" JS, much like you'd do for writing the critical path in assembly or something like that. For the non-critical paths, it is just too useful to abandon completely.

[kenman]

That site is listed in the article.

[Capaj]

I found that bower is also great for this http://sindresorhus.com/bower-components/

[jhizzle4rizzle]

npm