> However, it doesn't seem to not be an optimal solution for the case when I have 20+ "libraries" with a certain level of depth each having multiple nested modules/elements that also can reference
I think there's misunderstanding. I don't suggest copying the trees at import time. I suggest that "import element" would create a virtual node that references the external file symbolically. Then, the import could be "scoped to the subtree", so you might import "commons" library at the very top, and you could import more specific "libraries" somewhere inside the tree. > a challenge to properly resolve a tree assuming the external modules could potentially be cross-referenced Even though it sounds the most challenging task, it does not sound it is complicated. It should probably cache the referenced files to avoid reparsing on each click. Vladimir
