JavaScript ES7 Tutorial: Exponentiation and Array Membership

ES7 is a common name for ECMAScript 2016. Its additions include the exponentiation operator and Array.prototype.includes. Read their actual semantics and compatibility requirements rather than using the edition label to describe every feature that happened to become familiar around the same period.

Here's a popular JavaScript ES7 video — watch it, then summarize it with one click. Or paste any other YouTube link below.

— or paste your own YouTube link —

Want to keep the key points from a YouTube video? Paste the link below to turn it into structured notes.

Why Use JavaScript ES7 Tutorial: Exponentiation and Array Membership

Frequently Asked Questions

Does ES7 mean every JavaScript feature newer than ES6?

It identifies a particular language edition rather than an open-ended category. Later additions such as other syntax and APIs belong to their own editions, so name the actual capability when checking support.

Is exponentiation interchangeable with repeated multiplication in every expression?

The operator has specific precedence and associativity rules that affect compound expressions. Use explicit grouping when needed instead of assuming its visual similarity to another language guarantees the same parse.

How does includes express array membership?

It tests whether the array contains a matching value under its specified comparison behavior. Understand that behavior, including special numeric values, rather than equating it with every possible custom equality test.

Does includes compare two separately created objects by matching properties?

Object identity remains relevant under the membership operation. A separate object can contain equivalent-looking fields yet fail an identity-based membership check. Use an appropriate predicate when the application needs comparison by selected properties instead of reference identity.

Can syntax transformation alone supply a missing array method?

Transforming an operator and providing an absent runtime API are different compatibility tasks. Check both requirements for the target environment instead of assuming one successful build makes every ES2016 capability available.