Create a gist now

Instantly share code, notes, and snippets.

What would you like to do?
bling dot js


Because you want the $ of jQuery without the jQuery.

You may be interested in bling.js if you get tired of the [] document.querySelectorAll('.foo'), function(){ … rodeo. It does this:

// forEach over the qSA result, directly.
document.querySelectorAll('input').forEach(el => /* ... */);

// on() rather than addEventListener()
document.body.on('dblclick', evt => /* ... */);

// classic $ + on()
$('p').on('click', el => /* ... */);

It doesn't do anything else. This is not a jQuery equivalent.


  • on() works on elements, document, window, and results from querySelector & querySelectorAll.
  • $ is qSA so if you're grabbing a single element you'll have to [0] it.
  • Bling plays well with authoring ES6
  • Resig explored this stuff a while ago:
  • Bling doesn't work on Android 2.3 or iOS 5.0. Works everywhere else including IE8 (assuming Function.bind)

Nerdy implementation notes:

  • The NodeList prototype usually inherits from Object, so we move it to Array.
  • I'm curious how ES6/7 would let a NodeList be iterable and inherit from EventTarget
  • Setting Node.prototype.on = EventTarget.prototype.addEventListener is awesome. It works in Chrome/FF but not yet in IE/Safari.
  • I haven't set up any off() or trigger() to map to dispatchEvent & removeEventListener. I'm OK with that.
  • I'm using semi-standard for style. I tried standard sans-semicolons, but can't get used to it.
/* bling.js */
window.$ = document.querySelectorAll.bind(document);
Node.prototype.on = window.on = function (name, fn) {
this.addEventListener(name, fn);
NodeList.prototype.__proto__ = Array.prototype;
NodeList.prototype.on = NodeList.prototype.addEventListener = function (name, fn) {
this.forEach(function (elem, i) {
elem.on(name, fn);

paulirish commented Apr 30, 2015

It works!

thx browser-repl

cat bling.js test.js  | uglifyjs | pbcopy
repl safari
repl firefox
repl ie
repl chrome



    npm install -g browser-repl
    cat bling.js test.js  | uglifyjs | pbcopy   # copy bling & tests to clipboard
    repl  # see list of browsers to try it in
    repl ie
    # paste and zoooom!

var input1 = document.createElement('input') = 'one'

var input2 = document.createElement('input') = 'two'

$('input').on('click', function (e) {
  console.log('PASS!',, ' clicked! ')
window.on('click', function (e) {
  console.log('Pass! window received click too!')

// either click 'em or this is for testing…

function simulateClick (elem) {
  var evt = document.createEvent('MouseEvents')
  evt.initMouseEvent('click', true, true, window, 0, 0, 0, 0, 0, false, false, false, false, 0, null)
  var canceled = !elem.dispatchEvent(evt)


setTimeout(function () { simulateClick(input2)  }, 500)

andybak commented Jun 15, 2015

I had a few of these spare - you can have them: ;;;;;;;

goyote commented Jun 15, 2015

Who says we don't want jQuery? (serious q)

Because jQuery was born many years ago when browser implementations were very different, and much of the advanced functionality (like querySelectorAll) was not implemented. Now, there's very little reason for jQuery IMO, except for the syntax.

Why not return this on the ons to get the fluid interface back? Also .off

joa commented Jun 15, 2015

Nice! Maybe you can even use EventTarget.prototype.on instead of Node.prototype.on = window.on?

r-cyr commented Jun 15, 2015

I personally dislike the term "VanillaJS", I think of it as a disservice to the community because it confuses people into thinking that jQuery is not JavaScript. Perhaps we should start using the term "VanillaDOM" instead?

sukima commented Jun 15, 2015

Add ES6 Promises -> jQuery.Deferred API:

window.$.Deferred = function() {
  var resolver, rejector;
  var promise = new Promise(function(resolve, reject) {
    resolver = resolve;
    rejector = reject;
  var deferred = {
    resolve: resolver,
    reject: rejector,
    then: function(a, b) { promise = promise.then(a, b); return deferred; },
    pipe: function(a, b) { promise = promise.then(a, b); return deferred; },
    done: function(a) { promise = promise.then(a, b); return deferred; },
    fail: function(a) { promise = promise.catch(a); return deferred; },
    always: function(a) { promise = promise.finally(a); return deferred; },
    promise: function() { return deferred; }
  return deferred;

I thought it was never a good idea to extend a native object? I'm not questioning Paul's expertise, was just curious.

It's not that it's a bad idea to extend a native object - it's that you should do so fully knowing what problems that can cause. In fact there is a (very good) argument to be made (ie - it's supported by Douglas Crockford and Brandon Eich) that libraries are the best place to do so.

Extending Object and Array is fraught with peril for usage reasons but the others? Not so much.

see what i did one year ago:
1.) Simple: EventHandling + Delegation
2.) find method:


Your Readme indicates IE8 support, but I don't think IE8 has __proto__ support?


paulirish commented Jun 15, 2015

Nice! Maybe you can even use EventTarget.prototype.on instead of Node.prototype.on = window.on?

@joa, I wanted to but the EventTarget global isn't available everywhere. Probably a way to set it by walking a prototype chain instead, but I'm lazy.

Add ES6 Promises -> jQuery.Deferred API:

@sukima wow. that's hot. very nice. :)

Why not return this on the ons to get the fluid interface back? Also .off

@benjamingr could, but as there are no other APIs, no need. pretty simple life with a small feature set. :) off() is so uncommon, I'd be OK with using removeEventListener, but hey that's me.

sinan commented Jun 16, 2015

this seems like vanilla.js joke but it really shouldn't be more complex than this :) Start with this and extend it to whatever utility you need e.g. $.ajax = require('some-xhr-module')

niko commented Jun 16, 2015

Nice! A tiny bit of AJAX sugar would be nice.

maybe fetch wrapper for ajax and fetch-shim as dependency? ; D

Would be cool to take all the above suggestions, and add animations obviously.. oh wait that would be jQuery 2.x 😀

Nice sugar micro-library as is!

In case someone is interested, here's how to add very simple even delegation a-la jQuery. IE9+

Node.prototype.on = window.on = function (name, delegate, fn) {
  if(arguments.length !== 3) {
    return this.addEventListener(name, arguments[1]);

  return this.addEventListener(name, function (e) {
      return fn.apply(, arguments);

js-n commented Jun 16, 2015

@paulirish standard is neat, semi-standard is neat, but then there's also javascript whatever

JSila commented Jun 16, 2015

I implemented this behaviour just recently but not quite as elegant as this.
One note: IE8 lacks support for Array.prototype.forEach.

Love this implementation, you should turn it into a full fledged repo, you've got the code/readme/tests 😄

Was getting an "Object doesn't support property or method 'forEach'" in IE10/IE9 so I updated this lineNodeList.prototype.__proto__ = Array.prototype to NodeList.prototype.forEach = Array.prototype.forEach;

Combine this with promise.js and get "Promise Bling"?

Paul you are right. If I worked on nodes, lot of time, I have faced this kind of problem. This is the nice solution for [] But querySelector/querySelectorAll have some browser issue so for this have you any solution?

ebsen commented Jun 22, 2015

Line 9 is my favorite.

blaja commented Jun 24, 2015

I want moar! 😃 Great stuff.


ghost commented Jun 26, 2015

can be reffered to by its short url:

spiralx commented Jul 7, 2015

Line 9 should be replaced with the following:

Object.setPrototypeOf(NodeList.prototype, Array.prototype)

which is part of ES6 and currently supported in IE 11, FF and Chrome - for older browsers, this is a quick polyfill:

if (!Object.setPrototypeOf) {
  Object.setPrototypeOf = function(obj, proto) {
    obj.__proto__ = proto;
    return obj; 

Also +1 for Node.prototype.on and NodeList.prototype.on returning this, my versions are:

  Node.prototype.on = window.on = function(names, fn) {
    var self = this

    names.split(' ').forEach(function(name) {
      self.addEventListener(name, fn)

    return this

  NodeList.prototype.on = NodeList.prototype.addEventListener = function(names, fn) {
    this.forEach(function(elem) {
      elem.on(names, fn)

    return this

which also allow binding multiple events like jQuery e.g. node.on('change blur', function(ev) { ... } :)

have you tried ki.js? :D

Doing this is somewhat a bad practice:

NodeList.prototype.__proto__ = Array.prototype;

NodeList.prototype.on = NodeList.prototype.addEventListener = function (name, fn) {
  this.forEach(function (elem, i) {
    elem.on(name, fn);

Don't mess with the native prototypes!

Why don't you try it this way?

window.$ = document.querySelectorAll.bind(document);

Node.prototype.on = window.on = Node.prototype.addEventListener;

NodeList.prototype.on = NodeList.prototype.addEventListener = function (name, fn) { {
         elem.addEventListener(name, fn, false);

What about changing the prototype of HTMLCollection as well so they are easier to iterate over? You can find HTMLCollection's in properties like ParentNode.children

Not sure of the side effects, yet.

HTMLCollection.prototype.__proto__ = Array.prototype;

put code in github repo -
to make it open & conveninent for contribution

gugadev commented Oct 10, 2016

Better $ to querySelector and $$ to querySelectorAll instead of $('.something')[0].on(...).

Inspired by this to make a version here

What's new?

  • on applies to EventTargets and Arrays containing them, so you can do this:
$('*').slice(3).on('click', reveal );
$`div`.on( 'touchstart', dragOn ).on( 'touchend', dragOff );
  • NodeList and HTMLCollection both now delegate to Array
  • the on functions return this to allow chaining
  • and made it more ES5/6/7-y including Object.setPrototypeOf

These included ideas from @MadLittleMods and @spiralx and @joa

skylarmb commented Mar 1, 2017

@bjankord awesome. thanks for the tip. Sadly some of us do have to support IE9... 🎉

This does NOT work for DOM elements inside iframes. Here's the related SO question with a related code sample - based on the same principles as above code - with a reproducible example -
Any ideas anyone?

Ollie-w commented Jun 5, 2017

Is this safe to use in production?


paulirish commented Dec 2, 2017

@Ollie-w yeah totally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment