[tlrobinson]

That's still true but on the module level. If your module is so large that it's hard to keep track of the imports/requires then you should probably split the module up.

I really don't think require-ing within individual functions is a common or good practice. Can you point me to an open source project that does that?

[z3t4]

A module is already scoped in node.js. It would be nice to have scoped require in the browser too, instead of just global import.

Splitting up a program, or module, into (more) modules does not make it simpler, rather contrary, it makes it more complex! Unless it's a fully decoupled abstraction reusable in other projects.

An example of require-ing within individual functions: A function to send notifications to e-mail or SMS ... It makes more sense to require the SMTP or SMS module in those functions, then somewhere else.

[tlrobinson]

ES6 modules do get their own scope in the browser. That's kind of the point of them.