Hyeseong Kim

> it seems that it will also affect the module_systems for Dynamic import and should be taken into consideration. ~~The easy way is not to support it. Dynamic import is...

> I think package-specs can already be an array today, and we could just explicitly list commonjs and esmodule there? Right. I considered that too. Then it need to fuse...

Yep, we don't have a way to bind the JavaScript's [Disposable/AsyncDisposable and to use `using` keyword](https://github.com/tc39/proposal-explicit-resource-management) yet, which has recently reached stage 3 and TypeScript support.

AFAIK monadic let binding is one of the features we gave up in choosing a representation closer to JS. Support for some generalized syntax that's not common in JS is...

~~It would be efficient somehow for permanent map/set structures, but not sure for dicts~~ oh.. maybe I forgot to think about it in JS, it can simply be done with...

I understand there are concerns about drastically increasing the supported Node.js version How about dropping Node.js v15 or lower? We already do testing only on v16. (v16.x has complete ESM...

fyi what are new features in nodejs, useful for rescript peers and compiler itself. - [ESM support](https://nodejs.org/api/esm.html) (including TLW since v14.8.0): So we can convert our syntax into fully ES...

@cknitt done

A lot of follow-up work is possible to modernize our dev env and js wrapper

> Not sure if I should make a new issue for this, but since I saw this one I thought it could be a good option for a place. I...