The ES6 tests themselves should be written in pure ES3, except for the sole ES6 feature being tested (as well as any ES5 features strictly required to use the ES6 feature). ES Next tests may use any ES5 features that they wish, and only the ES6 features strictly required to use the ES Next feature.
The test code is placed in multi-line comments (as in this hack), so that Node.js can parse the data scripts without throwing syntax errors when encountering features it does not support. The build.js script will wrap the code in an eval call inside a try, so the tests themselves do not need to catch errors that non-supporting platforms may throw.
Most tests have a significance rating, which affects how a platform's total support percentage is calculated. A test rated "large" (representing a landmark, transformative feature) is worth 1, one rated "medium" (representing a significant feature that's less universally useful, or is primarily connected to another feature) is worth 0.5, and one rated "small" (representing a useful but subtle improvement from the previous spec) is worth 0.25. "tiny" (0.125) should be reserved for very meager changes (such as changes to an existing function's parameters or side-effects) that nonetheless don't fall under the category of another feature.
ECMAScript 6 compatibility table alternatives and similar libraries
Based on the "ES6" category.
Alternatively, view ECMAScript 6 compatibility table alternatives based on common mentions on social networks and blogs.
ES2015 [ES6] cheatsheet containing tips, tricks, best practices and code snippets
6.2 1.4 L5 ECMAScript 6 compatibility table VS LebabTurn your ES5 code into readable ES6. Lebab does the opposite of what Babel does.
Light speed setup for MEVN(Mongo Express Vue Node) Apps
Scaffolding utility for vanilla-js
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of ECMAScript 6 compatibility table or a related project?