TC39
tc39.es › ecma262 › 2021
ECMAScript® 2021 Language Specification
This Ecma Standard defines the ECMAScript 2021 Language. It is the twelfth edition of the ECMAScript Language Specification. Since publication of the first edition in 1997, ECMAScript has grown to be one of the world's most widely used general-purpose programming languages.
TC39
tc39.es › ecma262
ECMAScript® 2027 Language Specification
2 weeks ago - ECMAScript 2021, the 12th edition, introduced the replaceAll method for Strings; Promise.any, a Promise combinator that short-circuits when an input value is fulfilled; AggregateError, a new Error type to represent multiple errors at once; logical ...
09:57
JT du dev #1 - ECMAScript 2021 | :is & :where | #100DaysOfCode ...
Classes - Let's Learn ECMAScript 2021 with Earl Duque
02:26
Default Parameters - Let's Learn ECMAScript 2021 with Earl Duque ...
01:50
Conclusion - Let's Learn ECMAScript 2021 with Earl Duque - YouTube
04:05
Maps and Sets - Let's Learn ECMAScript 2021 with Earl Duque - YouTube
05:16
Let and Const - Let's Learn ECMAScript 2021 with Earl Duque - YouTube
Ecma-international
262.ecma-international.org › 12.0
ECMAScript® 2021 Language Specification - ECMA-262
This Ecma Standard defines the ECMAScript 2021 Language. It is the twelfth edition of the ECMAScript Language Specification. Since publication of the first edition in 1997, ECMAScript has grown to be one of the world's most widely used general-purpose programming languages.
W3Schools
w3schools.com › js › js_2021.asp
ECMAScript 2021
ECMAScript 2021 is supported in all modern browsers since April 2021: Promise.any() is a static method in JavaScript that takes an iterable of Promises as input and returns a single Promise.
TutorialsPoint
tutorialspoint.com › javascript › javascript_ecmascript_2021.htm
JavaScript ECMAScript 2021 Features
The ECMAScript 2021 standard was released in 2021. ECMAScript 2021 brought many notable features to JavaScript. The introduction of the String replaceAll() method simplified global string replacement.
Ecma International
ecma-international.org › wp-content › uploads › ECMA-262_12th_edition_june_2021.pdf pdf
ECMAScript® 2021 Language Specification
12th Edition / June 2021 · ECMAScript® 2021 · Language Specification · COPYRIGHT PROTECTED DOCUMENT · © Ecma International 2020 · Ecma International · Rue du Rhone 114 · CH-1204 Geneva · Tel: +41 22 849 6000 · Fax: +41 22 849 6001 ·
ServiceNow Community
servicenow.com › community › developer-advocate-blog › learn-ecmascript-2021-with-earl-duque › ba-p › 2804911
Learn ECMAScript 2021 with Earl Duque - ServiceNow Community
September 17, 2024 - Hi everyone, I'm Earl Duque, Senior Developer Advocate at ServiceNow, and I'm thrilled to introduce you to my video series titled "Let's Learn ECMAScript 2021." This series is a deep dive into the latest and greatest in JavaScript as it applies to ServiceNow, and I'm here to guide you through every step.
Ecma-international
262.ecma-international.org
ECMAScript® 2026 Language Specification
ECMAScript 2021, the 12th edition, introduced the replaceAll method for Strings; Promise.any, a Promise combinator that short-circuits when an input value is fulfilled; AggregateError, a new Error type to represent multiple errors at once; logical assignment operators (??=, &&=, ||=); WeakRef, ...
Reddit
reddit.com › r/servicenow › is there a reason not to use ecmascript 2021 at this point?
r/servicenow on Reddit: Is there a reason not to use ECMAScript 2021 at this point?
March 19, 2024 -
Like the title says - we have a number of scoped apps on our instance and I’m wondering when it makes sense to enable the newer version of JS. From what I can tell, enabling it should have zero negative impacts, as it allows for more capabilities in keywords and objects you can reference, but it doesn’t change the functionality of existing keywords.
With all that in mind, is there a reason why I shouldn’t just enable it across the board on my scoped apps? The main thing that crosses my mind is pseudo tech debt from existing code that would ideally be refactored to use the benefits of ECMAScript
Top answer 1 of 5
3
For new apps: no reason. In fact, it's on ECMAScript 2021 by default now for new scoped apps, if that's a good enough vote of confidence for it. For old apps that you are switching to the new version: it's mostly just making sure old code doesn't break: make sure no reserved keywords are variable names, like let, class, const, etc. make sure new scoped variables don't collide with global variables that already exist making sure old code doesn't have object properties/methods that don't uninentionally match any new shorthand syntax rare but if you have octal literals, the prefix changed regex, es6 had new flags so make sure your old regex patterns aren't accidentally triggering them (u for unicode, y for sticky, etc.) new methods and properties for built in objects, make sure your old code aren't already trying to define them (like Number.isNaN came in ES6) a lot of other changes involve strict mode but we don't do that in servicenow so i didn't list them. I made a playlist for SN developers to catch up to es21 if all they know is es5. https://www.youtube.com/playlist?list=PL3rNcyAiDYK1fUOYO83KOfF-NriBRAERV Sorry for the plug, but I thought it was relevant!
2 of 5
2
Ecma 2021 should be used wherever possible, if not used every piece of new code written into the instance is technical debt
Ecma International
ecma-international.org › accueil › standards › ecma-262
ECMA-262 - Ecma International
June 7, 2024 - Download this standardView in HTML ... 9th edition, June 2018 · ECMA-262, 10th edition, June 2019 · ECMA-262, 11th edition, June 2020 · ECMA-262, 12th edition, June 2021 ·...
ServiceNow
developer.servicenow.com › blog.do
Tokyo introduces ECMAScript 2021 (ES12/ecma6+)
August 8, 2022 - ServiceNow has denoted our version of JavaScript as ECMAScript 2021, which encompasses the feature roll-up of ECMAScript 6 to ECMAScript 12. To see the full documentation of changes, you can see the release notes here: JavaScript engine feature support.