Parcel: "http2" module

[nwtgck]

Hi, developers! Thank you for your very convenient project.

❔ Question

Could you tell me Parcel supports "http2" module?

🔦 Context

const http2 = require("http2"); causes an error "Cannot resolve dependency 'http2'".
require("http") worked well.

💻 Code Sample

Here is my index.js

// index.js
const http2 = require("http2");

http2.createServer((req, res)=>{
  res.end("hello, world\n");
}).listen(3000, ()=>{
  console.log("Listening...");
});

Here is how to build.

./node_modules/.bin/parcel build index.js --target=node --bundle-node-modules --no-cache

Here is the complete code: https://github.com/nwtgck/public-code/tree/master/parcel-http2

🌍 Your Environment

| Software | Version(s) |
| ---------------- | ---------- |
| Parcel | 1.12.3|
| Node | v10.15.0 |
| npm/Yarn | npm 6.8.0 |
| Operating System | macOS 10.12.6 |

[mischnic]

Parcel uses this list of node builtin modules: https://github.com/webpack/node-libs-browser/blob/master/index.js

EDIT: http2 and async_hooks are missing
It looks like we'll have to create our own version of that package because was actually deprecated a few days ago.

[DeMoorJasper]

Unfortunately that list is missing a lot more than just http2

[azz]

https://github.com/sindresorhus/is-builtin-module ?

[mischnic]

A package like that (a list of strings) isn't enough for our usecase, because some of these modules are actually polyfilled when bundling for the browser (e.g. buffer or path)

[azz]

Ah I see. Not possible to use a separate package for polyfills and determining builtins?

[mischnic]

Yes, I guess we could use some existing (maintained) package to make sure the builtin list is correct and use our own polyfill list

[devongovett]

We can use the list that is exported from node itself:

import {builtinModules} from 'module';

[Taym95]

Hey @devongovett, do you mean to use this package builtin-modules instead of node-libs-browser?

[mischnic]

Webpack 5 might remove automatic Node polyfills (https://github.com/webpack/changelog-v5#automatic-nodejs-polyfills-removed)

Instead, they should be explicitly aliased (and the version can be specified, outdated polyfills were a problem in the past):

{
    "dependencies": {
        "path-browserify": "1.0.0"
    },
    "alias": {
        "path": "path-browserify"
    }
}

Should we do the same for Parcel 2?

[devongovett]

Looks like this is fixed in #3620.

[jeduden]

Any chances this fix makes it into parcel 1.X ?

[SqueezeToyAliens]

I used this temporary solution.

Open node_modules/node-libs-browser/index.js and this line at the bottom:

I think that there are quite a lot of Parcel 1.X users out there who would like to use new NodeJS builtin modules. Is that possible to release a fix to the 1.X version?

[JoshGlazebrook]

2.x isn't even released, nor does it seem to be usable in its current state. Not sure why a fix for this isn't being pushed to 1.x... what the hell happened to this project?