Corey Farrell

@bmeck thanks for working on this. According to your readme `transformSource` is disabled, once that is not the case I can probably do some testing with your module (I haven't...

@bmeck I haven't had a chance yet to experiment with your compositional loader but I did finally get around to publishing https://github.com/istanbuljs/esm-loader-hook so we have something concrete which shows what...

I can understand arguments for and against node.js internals appearing in the stack, but that's not why I opened this issue. My concern is not so much the extra information,...

> > I added esm support for Mocha, and the trick I used to figure that out was to require the module, and if I got an error from node...

@giltayar the warning was not produced for dynamic import in 13.3.0 but this was fixed in 13.4.0 by nodejs/node#30720. If you are able to use `import()` in 13.4.0+ with no...

I've just published [get-package-type](https://github.com/cfware/get-package-type) v0.1.0 for this purpose. I need this functionality for nyc to support loading `nyc.config.js` where `type: module` applies. This package was implemented from scratch since the...

The default resolver hook is sync, should this instead be async? If it's ever desired to support loader stacking `node --loader=./loader1.js --loader=./loader2.js` I think this would be a blocker as...

I would not object to a PR adding a note to the README along with the other notes about lit-html usage in the `htmlMinifier` section. CC @LarsDenBakker not sure if...

Currently the matching logic is based on bindings, so when the plugin encounters `import {html} from 'lit-html';`, this creates a binding on `html`. Then when a template is tagged with...

If that can work I have no objection, I suspect this can be done in a semver-minor.