Is ES2023 Enough? A Look at the Game-Changers Coming in ES2024

Some of the latest features of ES2023 :

1. Array methods for searching from the end:

• findLast and findLastIndex methods: These methods work similarly to find and findIndex, but they start searching from the end of the array instead of the beginning. This can be useful for tasks like finding the last occurrence of an element or the last index that satisfies a given condition.

const array = ['a', 'b', 'c', 'b', 'a'];

console.log(array.findLast(element => element === 'b')); // Output: 'b'
console.log(array.findLastIndex(element => element === 'a')); // Output: 4

2. Symbols as WeakMap keys:

• WeakMaps can now use Symbols as keys in addition to objects. This provides more flexibility and can be useful for situations where Symbols are more appropriate than objects as keys.

const symbol = Symbol('MySymbol');
const weakMap = new WeakMap();
weakMap.set(symbol, 'Hello, world!');
console.log(weakMap.get(symbol)); // Output: 'Hello, world!'

3. Change Array by Copy:

• New methods on the Array.prototype such as toReversed(), toSorted(), toSpliced(), and with() allow you to make changes to an array and return a new copy with the changes applied, instead of modifying the original array. This can improve code clarity and avoid unexpected side effects.

const array = [1, 2, 3];
const reversedArray = array.toReversed(); // [3, 2, 1]
const sortedArray = array.toSorted(); // [1, 2, 3]
const splicedArray = array.toSpliced(1, 1); // [1, 3]
const updatedArray = array.with(1, 10); // [1, 2, 3] (original array remains unchanged)

4. Hashbang grammar:

• This feature standardizes the syntax for shebang lines (lines starting with #!) at the beginning of scripts. This allows for more consistent execution of scripts across different platforms.

#!/usr/bin/env node
console.log('Hello, world!');

While the exact features of ES2024 are still under discussion, here are a few possible additions that have been proposed or are under consideration:

1. Error Cause:

• This feature aims to provide a standardized way to access the underlying cause of an error, making it easier to trace the origin of errors and improve debugging.

2. Class Fields:

• This proposal aims to simplify the syntax for declaring class fields, making it more concise and readable.

3. Numeric Separators:

• This feature would allow the use of underscores as separators in numeric literals, improving readability of large numbers.

4. Ergonomic Brand Checks for Private Fields:

• This proposal aims to simplify the syntax for checking the brand of private fields, making it easier to ensure that code is accessing private fields correctly.

5. Top-Level Await:

• This feature would allow the use of await at the top level of modules, enabling cleaner handling of asynchronous operations without the need for wrapping code in async functions.

6. RegExp Match Indices:

• This proposal would add a matchIndices method to regular expressions, providing a way to retrieve the start and end indices of matches, along with the match itself.

7. String Normalization:

• This feature would provide methods for normalizing strings, such as converting them to a consistent case or removing accents.

8. Decorators:

• This long-awaited feature would allow the use of decorators to modify the behavior of classes and functions, potentially providing a more elegant way to handle common tasks like logging or authentication.

9. Interoperability with WebAssembly:

• This feature would enhance the interaction between JavaScript and WebAssembly, enabling more seamless integration of the two technologies.

10. Temporal API:

• This proposal would introduce a new API for working with dates and times, providing a more comprehensive and intuitive way to handle temporal data.

Sources