It is almost 2019 and people have generally come to the agreement that jQuery is deprecated. I for one have a very different perspective on that but that is for some other time. So why do people still use it? Old habits? Convenience? It turns out that the majority of people that use jQuery only use it for a select few methods.
I thought it'd be fun and educational for n00b programmers to re-implement those jQuery methods onto the HTMLElement prototype.
QuerySelector
Lets first define a shortcut for the document querySelectors. $ is for a single element and $$ is for all matches. We want to be able to provide a second context argument like jQuery that defaults to the whole document. I am assuming ES6+ where default values in function declarations are supported.
/**
* $ for document.querySelector
* $$ for document.querySelectorall
* with optional context just like jQuery (defaults to document)
*/
window.$ = (query, ctx = document) => ctx.querySelector(query)
window.$$ = (query, ctx = document) => ctx.querySelectorAll(query)
$('h2') // will return single _<h2>_ element
$$('h2') // will return array with all _<h2>_ elements
Using the context argument we can select all <p> elements within another element (<article></article>)
$$('p', $('article'))
NodeList iteration
You have to admit, the jQuery.prototype.each is pretty neat too. Add a property each to the NodeList prototype and set the value to a function that casts the NodeList to an Array and then iterates it using the callback function provided.
/**
* This allows you to "forEach" a NodeList returned by querySelectorAll or $$
* similar to jQuery.prototype.each
* use: $$('li').each(callback)
*/
Object.defineProperty(NodeList.prototype, 'each', {
value: function (fn) {
return Array.from(this).forEach((node, index) => fn(node, index))
}
})
Attributes
Another common jQuery method is attr. We can use attr to read and write attributes of elements in the DOM using a single method. We will add one tiny feature to our method. It returns all attributes when no arguments are provided.
With attr also comes removeAttr (remove attribute) and has to determine an argument exists.
/**
* single method to get/set/list attributes of HTMLElement.
* get argument id: $('div').attr('id')
* set argument id: $('div').attr('id', 'post123')
* list all arguments: $('div').attr() // Fuck yeah
*/
HTMLElement.prototype.attr = function (key, value) {
if (!value) {
if (!key) {
return this.attributes
}
return this.getAttribute(key)
}
this.setAttribute(key, value)
return this
}
/**
* remove attribute from HTMLElement by key
*/
HTMLElement.prototype.removeAttr = function (key) {
this.removeAttribute(key)
return this
}
/**
* check whether a DOM node has a certain attribute.
*/
HTMLElement.prototype.has = function(attribute) {
return this.hasAttribute(attribute)
}
innerText and innerHTML
/**
* single function to get and set innerHTML
* get: $('body').html()
* set: $('body').html('<h1>hi!</h1>')
*/
HTMLElement.prototype.html = function (string) {
if (!string)
return this.innerHTML
this.innerHTML = string
return this
}
/**
* single function to get and set innerText
* get: $('body').text()
* set: $('body').text('hi!')
*/
HTMLElement.prototype.text = function (string) {
if (!string)
return this.textContent
this.innerText = string
return this
}
Append and prepend
The following append method allows you to insert a HTML element at the end of the specified target element. The prepend method will insert it just before.
/**
* append HTMLElement to another HTMLElement
* like jQuery append()
*/
HTMLElement.prototype.append = function (child) {
if (child instanceof HTMLElement) {
this.appendChild(child)
return this
}
this.append(child)
return this
}
/**
* prepend HTMLElement to another HTMLElement
* like jQuery prepend()
*/
HTMLElement.prototype.prepend = function (sibling) {
if (sibling instanceof HTMLElement) {
this.parentNode.insertBefore(sibling, this)
return this
}
this.parentNode.insertBefore(sibling, this)
return this
}
Removing elements
Removing an element in JavaScript happens by accessing its parent node to call removeChild(). Yeah weird I know.
HTMLElement.prototype.remove = function() {
this.parentNode.removeChild(this)
}
As you probably know, you can not use arrow functions in jQuery. However
$('#foo').remove()
// or
$$('div').each(element => element.remove())
Parent
Get the parent of a node.
/**
* get a HTMLElement's parent node
* use: $('h1').parent()
*/
HTMLElement.prototype.parent = function () {
return this.parentNode
}
Events
Modern JavaScript libraries implement on, off and emit to get, set and dispatch events.
/**
* add event listener to HTMLElement
* $(document).on('click', event => ...)
*/
HTMLElement.prototype.on = function (event, callback, options) {
this.addEventListener(event, callback, options)
return this
}
/**
* remove event listener from HTMLElement
* $(document).off('click', callback)
*/
HTMLElement.prototype.off = function (event, callback, options) {
this.removeEventListener(event, callback, options)
return this
}
/**
* dispatch an event on HTMLElement without needing to instanciate an Event object.
* $(document).emit('change', { foo: 'bar' })
*/
HTMLElement.prototype.emit = function (event, args = null) {
this.dispatchEvent(event, new CustomEvent(event, {detail: args}))
return this
}
DataSet
And last but not least a nice method to access data attributes.
/**
* single method to get/set/list HTMLElement dataset values
* get: $('div').data('color') assuming <div data-color="..."></div>
* set: $('div').data('color', '#0099ff')
*/
HTMLElement.prototype.data = function (key, value) {
if (!value) {
if (!key) {
return this.dataset
}
return this.dataset[key]
}
this.dataset[key] = value
return this
}
Define
This is unrelated to jQuery but still a nice shortcut.
/**
* Convenient shortcut
* use: define('property', { ...descriptor })
*/
Object.defineProperty(window, 'define', {
value: (property, ...meta) => meta.length == 2 ? Object.defineProperty(meta[0], property, meta[1]) : Object.defineProperty(window, property, meta[0]),
writable: false,
enumerable: true
})
Now we can do for instance this:
/**
* now | single statement accessor that returns current time
* @returns {number}
*/
define('now', {
get: Date.now
})
The identifier now will return the current time. You don't have to call it as a function, simply accessing it will do.
setInterval(() => console.log(now), 10)
/*
1543930325785
1543930325795
1543930325805
1543930325815
1543930325825
1543930325835
*/
Gist
For your convenience, a gist with all that is above.
https://gist.github.com/jochemstoel/856d5b2735c53559372eb7b32c44e9a6
Top comments (22)
Some notes:
$$('p', $('article'))
returns all<p>
elements in the first<article>
, not all<p>
s that are children of<article>
s. For that you'd still have to do$$("article > p")
HTMLElement.prototype.has = HTMLElement.prototype.hasAttribute
doesn't bind the function properly, sothis
will not work properly.text()
function should use.textContent
not.innerText
HTMLElement.append
should still check to see ifchild
is an instance ofNode
, even if it's not anHTMLElement
HTMLElement.prototype.prepend
HTMLElement.prototype.prepend
, already existsHTMLElement.prototype.remove
already exists tooHTMLElement.prototype.parent
should return.parentElement
HTMLElement.prototype.emit
should haveargs=null
as a parameter and usenew CustomEvent(event, { detail:args })
HTMLElement.prototype.append
andNodeList.prototype.forEach
already exist, too.Thanks I fixed the things you said in updated gist. Why does text need to return textContent and not innerText?
innerText
is a lot more performance heavy and triggers layout to be recalculated.stackoverflow.com/a/35213639/5203655
AFAIK,
innerText
is also non-standard (originally IE-only) whereastextContent
is part of the standard.Nice write-up of extending the base prototypes!
I do have a bit of a hang-up with modifying prototypes of builtins without using
Object.defineProperty
, though. If any application is inspecting the prototype, those properties are enumerated, so it might be better to define them as non-enumerable on the prototype object, just to be on the safe side. A factory function that would augment a built in by taking a property name and a function would make the examples just as readable. :)I love articles like this that make it clear just how thin an abstraction layer you can have on top of the standard web API.
It also gives you an idea on what Babel does under the hood.
A word of warning:
ParentNode.append()
andParentNode.prepend()
, which have bazonkers browser support (everything but IE), behave likeNode.appendChild()
(But can take strings, and multiple nodes) and not like$().append()
.The sibling addition behavior, like the
$().append()
is implemented asChildNode.after()
andChildNode.before()
. It has the same affordances as theParentNode.append()
but is less supported (No Safari, no mobile Edge)I think you should test if string is undefined in
html()
andtext()
, otherwise it wouldn't be possible to set it empty.PS: I am commenting from my phone, so forgive the lack of details :)
If HTML and/or TEXT is empty you want to return the innerHTML and innerText so no.
How would you simulate jQuery
$('#el').html('');
?You can literally use my example already provided in the post:
then
That wouldn't work because
''
would evalute tofalse
and in your code it would be the same as$('#el').html()
.Check it running: codepen.io/fernandosavio/pen/qLWeWV
Well whatta ya know. You are right.
Change the line
into this
so that you get
codepen.io/jochemstoel/pen/OrJLbR
You can also replace it with
or even
Not sure if you've ever used it, but this is basically the approach Prototype.js took (and MooTools copied). The issue back in the Prototype.js era was that extending the native prototypes didn't work in IE6, so it had to also support a different approach (a wrapper object) in IE.
Below is the suggestion from ChatGPT that I requested it.
I used jQuery exclusively for
$.ajax()
(yeah, i know. But i’m not a front-end dev) until i finally took some time and learn aboutXMLHttpRequest
. And now there’s this Fetch thing…elmenet.attr('min', 0)
will return the attribute value.better check
arguments.length
These are very nice! Have you also tried implementing Ajax calls and stuff without jQuery? For a long time those were a big reason for sticking with jQuery but then Fetch API came.
No I did not, for the reason you mentioned. We have fetch nowadays. Would you like me to, though?
Yes that would be a cool post
How can it be implemented in angular?