ExperimentalWarning: The http2 module is an experimental API. about grunt-contrib-connect

[Doacola]

With NODE_NO_HTTP2=1 in environment variables I tested with latest LTS v8.9.1 the warning is no longer visible but seems like it was not added or just doesn't work in v9.0.0 or v9.1.0 (Both of them were tested).

So if that warning causes that much trouble just up-/downgrade to v8.9.1LTS and that environment variable will remove the message.

So this issue is not directly caused by grunt but instead it's based on latest updates from Node and their decision to add http2 to be exposed by default.
https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V8.md#2017-10-24-version-880-current-mylesborins

[IceCreamYou]

The OP notes the env variable workaround, but that's not a viable solution for code that needs to be distributed to others. We can't ask every user of the code to add this variable.

More importantly, setting the env variable causes grunt-contrib-connect to use the userland package which is now deprecated. It'd be nice to move onto code that will be maintained.

[toptalo]

Get same warning on v8.9.0 (current LTS)

[cssagogo]

Get same warning on Node v9.0.0 and NPM v5.5.1

[knoxcard]

Does not work on v9.2.0 either, when will this be corrected? http2 is commonplace.
It prevents my entire web platform from loading, instead a 502 Bad Gateway is returned from my frontend proxy server NGINX.

Reverting back to v8.7.0.

Any version above node v8.7.0 does NOT work for me.

[XhmikosR]

This is gone with the latest master changes, will be in v2.0.0 when it's out.