Learn about JavaScript's new .at() method, its use cases, and how it can improve developers’ experiences compared to preexisting methods.

LogRocket is a frontend monitoring platform that helps developers debug and troubleshoot issues in web applications by providing session replay, error tracking, and performance monitoring capabilities. With LogRocket, developers can gain insights into user interactions, identify bugs, and optimize application performance to deliver better user experiences. Developers can learn how to integrate LogRocket into their web applications, analyze user sessions, and diagnose frontend issues effectively.

LogRocket

The JavaScript .at() method was introduced in the August release of the ECMA International TC39’s relative indexing proposal. It allows developers to grab elements based on their indexes. In this tutorial, we’ll look at the benefits and drawbacks of the .at(), and how it can improve developers’ experiences.

Using the new JavaScript .at() method

Existing methods for getting list elements

We made a custom demo for . No really. Click here to check it out .

LogRocket : Debug JavaScript errors easier by understanding the context

Really wish Safari would stop dragging their feet on supporting awesome methods like this.

Basically
const myArray = [0,1,2];
console.log(<a href="http://myArray.at" target="_blank" rel="noopener nofollow">myArray.at</a>(1));
//is the same as
console.log(myArray[1]);
Only case that could be a problem is if the object has a property with -1 as key… which the odds -in my opinion- are quite low

This is the best method I’ve ever seen!

TL;DR, <code>Array.prototype.at(Integer)</code> allows negative indexes, so <code>.at(-1)</code> is the last item of the array. Not supported in all browsers