1207892 - NodeJS in browser support tables

Status: RESOLVED FIXED

(Developer Documentation Graveyard :: General, defect)

Description

[p.christidis]

:: Developer Documentation Request

      Request Type: New Documentation
     Gecko Version: unspecified
 Technical Contact: 

:: Details

Not a bug, just a documentation request.
Could you add nodejs to the supported browsers tables for the JavaScript reference documentation?

Comment 2

[Florian Scholz (Open Web Docs)]

While we could start to add Nodejs support information to the current wiki pages, this needs coordination with the Compat Data API project. Moving there for discussion.

Comment 3

[Jean-Yves Perrier [:teoli]]

Node being base on V8, I guess we could populate node.js values from Chrome values (using a conversion table) in the Compat Data DB.

I guess manually adding them to each JS page now will be overkill.

Ni/ Renoir for his insight here.

Comment 4

[Eric Shepherd [:sheppy]]

I agree that having Node.js listed would be good. It's becoming extremely popular, and having a mapping of its versions to the inherited V8 functionality in that release would be crazy helpful.

Comment 5

[Renoir Boulanger [:renoirb]]

Agrees.

I'll keep this bug opened and update it once I find a way to fill this requirement.

Comment 6

[Florian Scholz (Open Web Docs)]

(In reply to Jean-Yves Perrier [:teoli] from comment #3)
> Node being base on V8, I guess we could populate node.js values from Chrome
> values (using a conversion table) in the Compat Data DB.
> 
> I guess manually adding them to each JS page now will be overkill.

There is also nodejs with the Chakra engine. https://github.com/Microsoft/node
Wondering if it makes sense to talk about engines in the future.

Engines: SpiderMonkey/Gecko, Chakra, v8/blink, WebKit/jsc
Environments: desktop, mobile, "server"(?)

Comment 7

[Jeremie Patonnier :Jeremie]

(In reply to Jean-Yves Perrier [:teoli] from comment #3)
> Node being base on V8, I guess we could populate node.js values from Chrome
> values (using a conversion table) in the Compat Data DB.

Unfortunatly that's not that easy. First of all, it's pretty hard to match the V8 version used by a given chrome version and the one used by a given NodeJS version. NodeJS also allows to use some V8 features that are not yet shipped with Chrome. That induce the requirement to handle NodeJS as a fully independent environment.

(In reply to Florian Scholz [:fscholz] (MDN) from comment #6)
> There is also nodejs with the Chakra engine.
> https://github.com/Microsoft/node
> Wondering if it makes sense to talk about engines in the future.

I don't think so. That build is an MS fork that is not part of the official NodeJS build. As long it's not an official maintained product, it makes very hard to track compatibility information.

But the biggest issue is that tracking JS engine does not really provide any useful information about the actual support within a user facing product: Each running environnement (browser or node) can activate or not different features of a same engine. As a consequences, knowing which feature is supported by a given JS engine doesn't really help to know what will work or not :-/

Comment 8

[John Whitlock [:jwhitlock]]

The BrowserCompat project is canceled.  The current effort is at https://github.com/mdn/browser-compat-data, and looks to have initial Node.JS support:

https://github.com/mdn/browser-compat-data/blob/cc7d6b63ce421c5ba58c5c6abed769d636ee215d/javascript/promise.json#L33-L35

Comment 9

[Florian Scholz (Open Web Docs)]

Browser compat data for ECMAScript has nodejs, https://github.com/mdn/browser-compat-data/tree/master/javascript
The new tables (soon for beta users) display nodejs, https://discourse.mozilla.org/t/beta-testing-new-compatability-tables/21269

Please contribute nodejs versions to files in https://github.com/mdn/browser-compat-data/tree/master/javascript