So far, just two options were considered to specify the location of a module to load in an import statement, relative to the importing module and absolute path:
//relative to current module
import DOMList from "./lib/jQueryList"
//absolute path
import DOMList from "c:/wwwroot/myWbSite/lib/jQueryList"
Absolute paths should be avoided since copying or moving the whole file tree into a different location would break the code, so the only viable option analyzed was a path relative to the importing module. Organizing the whole code with relative paths is straightforward if one has full control of how to place each file.
Unluckily, this is not the the case when one uses third-party libraries with their own import statements and their own dependencies, since library authors don't know where their files will be placed, and where the files of other...