Add "Modules Tab" to Compat Table

[ghost]

Prior to the addition of https://github.com/kangax/compat-table/issues/1052 a modules tab has been requested.

[ghost]

@ljharb Thanks for championing and pressing on proper organization of the Compat Table. Before a Tab is added, would you be able to provide some vision on what such a tab might look like and what sorts of sections it might include? /cc @domenic

When talking about a "tab", is this what is meant?

[ljharb]

Yes, that's exactly what is meant by "tab" :-)

My thoughts:

For import/export statements, I'd assume that one would need to research into each environment, how it exposes the Module parsing goal, and then find a way to invoke a shared set of tests in the Module parsing goal.

For import(), one would need to research, for a given engine, what a "successful" and a "failed" dynamic import path would be, and then use those paths with a set of shared tests.

[chharvey]

any updates on this?

es6+ module support has improved dramatically over the past 2 years, and this feature would add a lot of important information that the table is currently missing.

[ljharb]

A PR to add a Modules tab would be welcome.

[justinfagnani]

How would this be made to integrate with stage and language-year organization? ie, import() and import.meta are part of ES2020, import assertions are Stage 3, export v from "mod"; is Stage 1, etc.

Even with a modules tab, I would hope to also see those in the language-year sections to have a better idea of environment support for a given year.

[ljharb]

@justinfagnani i think there could be some kind of link in the relevant sections pointing to the modules tab - and within that tab, we'd certainly want to indicate at what stage something is.