Fails to support object destruction about circular-require HOT 3 CLOSED

This module relies heavily on module-deps for parsing, and that module unfortunately doesn't support many ES6isms and isn't getting any significant maintenance. I'll likely deprecate this module, especially because ES6 import/export syntax supports circular requires.

from circular-require.

Circular requires were allowed also before ES6, your milage depends a bit on how you consume them (e.g. nodejs vs. browserify).

They remain a bad idea, in particular they can cough up mysterious errors at import time that are hard to track down once your dependency graph is lange enough. Apart from general code smell and unclear responsibilites, of course. Nothing special to Javascript or ES5/6/(n+1), also holds true for Python or any other dynamic language.

from circular-require.

Yep, that's true and afaik this module doesn't claim they're forbidden or disallowed. ES6 import/export syntax is materially different in its handling of cyclical dependencies and the spec is much clearer about behavior - but, sure, still a bad idea.

That said, this is a wontfix issue on an up-for-adoption repo, so... closing.

from circular-require.