Not sure I see what you're saying. Requires are impossible to statically analyze in some pathological cases, which is why more rigidly defined imports made it

Not sure I see what you're saying. Requires are impossible to statically analyze in some pathological cases, which is why more rigidly defined imports made it into the ES2015 spec. That's totally unrelated to classes vs. functions or any of the other things you've mentioned.