JSNativeLoadSpec
Related Docs:
class JSNativeLoadSpec
| package Trees
Load from the global scope.
Load from the global scope.
The path is a series of nested property names starting from the
global object.
The path can be empty, in which case this denotes the global object itself.
Any element in the path is a property selection from there. A global scope loading spec with one path element is therefore a global variable.
Examples:
//Global(None, Nil) // .Date Global(None, List("Date")) //.cp.Vect Global(None, List("cp", "Vect"))
Load from a module import.
Load from a module import.
The module is the ES module identifier. The path is a series of
nested property names starting from the module object.
The path can be empty, in which case the specification denotes the namespace import, i.e., import a special object whose fields are all the exports of the module.
Any element in the path is a property selection from there. A module import info with one path element is importing that particular value from the module.
Examples:
// import { Bar as x } from 'foo' Import("foo", List("Bar")) // import { Bar as y } from 'foo' // y.Baz Import("foo", List("Bar", "Baz")) // import * as x from 'foo' (namespace import) Import("foo", Nil) // import x from 'foo' (default import) Import("foo", List("default"))
Like Import, but with a Global fallback when linking without modules.