Support for node native HTTP2 module

Issue details

Please update browser-sync so it no longer seeks for a third-party node module when you set httpModule: 'http2', but instead uses the node native one.

Please specify which version of Browsersync, node and npm you’re running

• Browsersync [ ^2.23.6 ]
• Node [ v9.6.1 ]
• Npm [ 5.6.0 ]

Affected platforms

• linux
• windows
• [ X ] OS X
• freebsd
• solaris
• other (please specify which)

Browsersync use-case

• API
• Gulp
• Grunt
• [ X ] CLI

If CLI, please paste the entire command below

node ./.tasks/browsersync.js

for all other use-cases, (gulp, grunt etc), please show us exactly how you’re using Browsersync

    httpModule: 'http2',
    https: {
        key: `${ os.homedir() }/.ssh/key.pem`,
        cert: `${ os.homedir() }/.ssh/cert.pem`
    },

[aj-dev]

@shakyShane any news on Node’s built-in HTTP2 support? The LTS release v10 is out so it’s not in experimental mode anymore.

[lunelson]

@jfstephe my solution from back then probably depends on the specific versions of the resolve and http2 packages at the time. NOTE that @dman777 is using require.resolve in his code above; but this will get the native module not the 3rd party one. You need resolve.sync from the resolve package. OTOH @Andrew-Bx 's insight about createSecureServer vs createServer looks like a better fix if it works