Skip to content

gbrail/node-compat-table

This branch is 13 commits ahead of, 95 commits behind williamkapke/node-compat-table:gh-pages.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

13d80cf · Dec 31, 2024
Mar 22, 2023
Dec 16, 2024
Dec 31, 2024
Feb 10, 2016
Jun 29, 2020
Feb 10, 2016
Aug 14, 2018
Mar 20, 2023
Nov 17, 2017
Nov 17, 2017
Jun 29, 2020
Feb 24, 2017
Apr 18, 2017
Jan 6, 2022
Feb 26, 2017
Jul 18, 2016
Jul 25, 2019
May 4, 2016
Dec 31, 2024
May 31, 2022
May 4, 2016
Nov 12, 2024
Jan 6, 2022
May 4, 2024
Nov 17, 2017
Dec 31, 2024
Aug 14, 2018
Jan 6, 2022
Dec 31, 2024
Dec 31, 2024
Dec 17, 2024
Mar 21, 2023
Mar 20, 2023
Mar 21, 2023
Apr 12, 2021
Nov 12, 2024
Jul 25, 2019
Dec 11, 2024
Jun 6, 2017
Feb 17, 2017

Repository files navigation

Node.js ECMAScript compatibility tables

node-compat-tables is built on top of Kangax's hard work. The majority of the credit needs to be given to the contributors of that project.

Although Kangax's compat table is amazing, it focuses on the entire Javascript ecosystem. As a Node.js developer- I, thankfully, do not need to be super concerned with all of the flavors out there. What I do need are deeper insights in the variations across the fast moving versions of Node.js. So, I created node-compat-table.

It works by running a script that imports the latest set of ES6 ES2015, ES2016 and ES2017 tests from the compat-table project and running them against several versions of node PLUS the nightly build. The results are committed/published here.

CLI or programmatic using

There is a Node.js module which you can programmatically check the compatibility. Also, there is a CLI program done this work.

For details, you can check out the two repositories below:

  • node-green - Check Node.js ECMAScript compatibility programmatically.
  • node-green-cli - CLI program for checking Node.js ECMAScript compatibility.

Making change to the webpage

The webpage is hosted via GitHub.

The build.js file:

  1. aggregates the data from the /results folder for the versions listed in v8.versions
  2. uses index.pug to generate index.html

So, change index.pug then run:

$ node build.js

** Note: If a version is listed in v8.versions that doesn't have results generated in the /results directory, the column will be empty (all white cells- no text).

How tests are run

A scheduled task runs on GitHub Actions runs bash test.sh once a day, which saves the results to the /results directory, rebuilds the webpage.

It then push the changes to the GitHub repo when complete.

js-standard-style

License

MIT Copyright (c) William Kapke

About

node.green - Node.js ECMAScript compatibility tables

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • HTML 98.9%
  • Other 1.1%