Caniuse: Show info about Node.js

[piranna]

Add Node.js as one of the "browsers" to know what features are available in what version. If _browser_ is not a valid section, it could be added a new "servers" one that could allow in the future add info about Rhino and Chakra.

[alinnert]

Do you know http://kangax.github.io/compat-table/es6/ ?
It's a compatibility table especially for ECMAScript standards. It already includes node.js and other servers.

I don't know if caniuse is the right place for node. Caniuse is also targeting HTML and CSS which doesn't apply to node at all.

[piranna]

Do you know http://kangax.github.io/compat-table/es6/ ?
It's a compatibility table especially for ECMAScript standards. It already includes node.js and other servers.

I know about it, but always found caniuse more complete and easier to use.

I don't know if caniuse is the right place for node. Caniuse is also targeting HTML and CSS which doesn't apply to node at all.

Good point, I like that distinction. Obviously Node.js will not have support for HTML and CSS, at least without usage of external modules...

[alinnert]

more complete? Well, the compat-table only covers ECMAScript as the language itself (which is system independent). That doesn't contain APIs (which differ a lot between server and browser). Do you mean that? But I don't think that's a bad thing. Caniuse is more APIs focused, although it also lists a few ES features.

[jimmywarting]

I would also like to see stuff about NodeJS features in caniuse.com would be really useful.
Can not find any information when String.prototype.startsWith got shipped to NodeJS - So i don't know what i should set my lowest Engine to in package.json

v5 have a rapid release cycle. compat-table only covers 2 node versions. so a automatically test process like caniuse's would be sweet

[Mottie]

There is also https://node.green/ - but I think it would be nice to have nodejs info on caniuse.

[piranna]

There is also node.green - but I think it would be nice to have nodejs info on caniuse.

I know of node.green, but seems to be only focused on EcmaScript functionality provided by v8, not about other APIs like URL objects.

[HopefulLlama]

Is there any further movement on this?

I'd also be in favour of NodeJS and other server-side technologies included.

[forresthopkinsa]

CanIUse is part of my normal workflow when working with JS, it would be convenient to not have to use a different site when working on Node

[alinnert]

That's an old issue... 😀 I do have a very different view on this matter now.

The thing is that Node.js can be split into two parts: ECMAScript features and Node.js APIs. Currently CanIUse is focused on browsers and therefore ES features. Adding Node.js APIs would drastically increase the scope of this project and also Browsers don't give any results for these APIs. This is a point where I wonder if the current UI still makes sense if Node.js APIs get added.

[piranna]

Node.js is adding more W3C APIs each time, like EventTarget or AbortController or WebCrypto for compatibility purposses. Also, deno APIs are exclusively based on W3C APIs and from their IDLs by design, so it makes also more sense. If we allow third party libraries and polyfills in the mix for things like fetch API or WebRTC or WebAudio, definitely it makes total sense to show info about Node.js support for these APIs :-)