I was surprised to find that in Babylon I can have two import modules with each other without any problems. I have found several places that refer to this as a well-known and expected behavior in Babylon. I know this is widely considered an anti-pattern by many (I guess most) people, but please ignore this for this question:
import
Does anyone know if this (or will) be the correct behavior in ES6 / 7?
The closest thing I can find in the official answer (and technical explanation) is this comment on 2ality.com
This is usually considered a bad experience. But ES modules are designed to support circular dependencies. There is some information in the ES 2017 specification 15.2.1.16.3 ResolveExport Concrete Method . However, it seems to me that it is very difficult to read (to be honest, I suffer a lot). The message you mentioned on 2ality.com may be more readable.
I work with nodeJS, so this is the same. From what I know, โrequired cyclesโ are not illegal, even if they are often best avoided. If there is a loop, nodeJS will at least handle this: it will not require a second time.
Source: https://habr.com/ru/post/1011971/More articles:Conflicting implementations of characters, even if related types are different - genericsBootstrap 4 Several carousel items (several carousel items shown immediately) - cssHow to configure java code to answer my own project on intellij? - androidA way to get the absolute path to a PHP file - phpPermission denied by Google Tagmanager Android - androidWorks on Simulator, does not work on device: error: WatchKit application does not contain any WatchKit extensions - objective-cDense rank with order - sqlNSExtensionPointIdentifier error only on real device - watch-ossipjs and asterisk sound call do not sound - webrtcReact Native - How to add and add data to a ListView without fully reprocessing - appendAll Articles