Aug 26, 2017 · 1 min read
Well yeah, if you use it against two different versions of the same class defined in two different closures it definitely won’t work. It’s a recursive reference check against the inheritance chain. It works as intended. I think it might get hairy in the browser due to duplicitous code created from a malformed build step, but in Node it works perfectly and with no issues due to typical commonjs setups. I think what you are describing is an issue with tooling not an issue with the language itself
