Bradley Farias

> Leverages the work @bmeck has done to expose it as a named export import { require } from 'module' I have not worked on the `require` named export, just...

@WebReflection `import()` is in all grammars of ECMA262. Its placement is valid in any [CallExpression location](https://tc39.github.io/proposal-dynamic-import/#prod-CallExpression)

@WebReflection the fact remains that `import()` is valid syntax in CJS (heck it is even valid in `eval`) but static `import` declarations are not valid syntax in CJS. I don't...

> Please find me a published NodeJS npm module that uses it. I can't because no environment supports it. Babel and Webpack based compilation do not implement it as spec...

There are also discussions of loader hooks ala https://github.com/nodejs/node/pull/15445 ; I would want strong discussions to take place around use cases since as @jdalton has stated, no one party seems...

@jmeas I would be hesitant to encourage such a broad change, almost everything on `npm` doesn't work like real ESM even if it uses the grammar and such breakage means...

got a discord channel if people want to chat in there: https://discordapp.com/channels/350004786915180548/359451835779514378

@mcollina 1. the task runner in C++ doesn't quite match the behavior of the shim I did to make it work with the JS based watch mode (perhaps this is...

@anonrig said via [twitter](https://x.com/yagiznizipli/status/1805418718014620024): > I think this is not the correct solution. We should reuse the existing task runner implementation instead of having 2. I could take a look...

You should feel free to ignore http/s imports most likely. Having a sync shared worker behind the hook seems fine and to my knowledge no adoption of network imports gathered...