Breaking cycles from transpiler plugins should be possible by doing the following:
When a transpiler plugin calls load.fromText(), track that module as a dependency/special value for that plugin resource ID, so that the exports for that module can be used as the value for the plugin resource ID when breaking cycles.
Transpiler plugins are the only ones that should have this problem, other loader plugins are for dead-end resources. The cycle detection can stay ignorant of them.
Marking this for 2.0.3, but may push to 2.1 depending on the code change needed for it.
Breaking cycles from transpiler plugins should be possible by doing the following:
When a transpiler plugin calls load.fromText(), track that module as a dependency/special value for that plugin resource ID, so that the exports for that module can be used as the value for the plugin resource ID when breaking cycles.
Transpiler plugins are the only ones that should have this problem, other loader plugins are for dead-end resources. The cycle detection can stay ignorant of them.
Marking this for 2.0.3, but may push to 2.1 depending on the code change needed for it.