Christopher Hiller

> As you've already noticed the Jasmine tests are in a bit of a stuck state due to the out of date libraries. I was never able to find a...

to be clear, I think what we're talking about is not the browser, or how a bundler must work around the limitations, but rather what Node.js can add (beyond the...

Per our discussion, this is what's needed: 1. A module needs to know _which module_ imported it. - If module `a` imports module `b`, we should be able to query...

I'll let @theKashey explain.

(if he doesn't want to: in a nutshell, I think it has to do with being able to mock one "use" of a module, but not another)

> Is it worth “polluting” core with that? unequivocally, YES

> If the requirements could enumerate either in words or js code the conditions that should be trapped and forwarded to a termination handler, that would be handy ^ next...

I need to enumerate the list of cases this should cover, and I haven't done that yet.

is [node-environment-flags](https://npm.im/node-environment-flags) (a polyfill for `process.allowedNodeEnvironmentFlags`) something that belongs in the `nodejs` org?

@iansu and @bcoe were trying to get a shim into package `mkdirp` but it doesn't sound like substack was interested.