ECMAScript 2022: New Exciting JavaScript Features

This ES2022 tutorial is going to break down the new JavaScript features of 2022 such as "top-level await", "private class fields", ".at()" and so on.

======⚡⚡⚡======
======⚡⚡⚡======

📚 Resources:

🕒 Timestamps:
(00:00) ECMAScript 2022
(00:46) Top-level await
(04:00) Class fields
(06:49) Error cause
(08:01) .at()
(09:45) .hasOwn()
(10:35) RegExp 'd' flag

And don't forget to subscribe for more videos like this 😊

#ecmascript2022

[keshavakumar]

by far the best update. thank you for explaining in less that 10 mins . Awesome content!

[kraftwerk]

The double 'function' at 11:20 is there, because the array from .match() always contains the whole matched string, then a string for every capturing group (if any). The is a capturing group and it represents the second occurence of 'function'

[TodorescuProgramming]

this is actually the video I was having on the planning sheet to make, great content! keep it up

[dewinchy]

if using static - at least in other programming languages - you should NOT access the variable by "this.", but by it's class name, so at 6:30 I would've used Example.seed = 5

[chrisalexthomas]

So to make class fields private you add a hash, but to make a field static you add a static keyword. That sounds terrible. Even if the functionality is welcome.

[TroenderTass]

No, no I'm not exited for the upcomming features just like you. Infact, the at function is a perfect example of adding bloat to a language and "fix" a problem that was never there. You will never not know the lenght of an array in javascript, and you will always easily be able to find items from the end of the array by that. Why don't they start introduce something useful, like enums?