Can we add some tests with a function that's called "require" but isn't the global one?

constrequire=(x)=>{};consta=require("./a.js");

This require would be detected as the global require even though it isn't.

This is indeed a limitation of my implementation but I thought it would be acceptable since the following rules also have the same limitation:

• no-dynamic-require
• no-amd
• max-dependencies
• no-self-import
• no-relative-packages

Hmm - are there no rules thatdont have the limitation?

I am not aware of any and even themoduleVisitor util has that limitation