Type Members

1.  final class CommonPhaseConfig extends AnyRef

   Common configuration given to all phases of the linker.

2.  final class CoreSpec extends AnyRef

   Core specification for the Scala.js code.

3.  final class LinkedClass extends AnyRef

   A ClassDef after linking.

   A ClassDef after linking.

   Note that the version in the LinkedClass does not cover methods nor exportedMembers as they have their individual versions. (The collections themselves are not versioned).

   Moreover, the version is relative to the identity of a LinkedClass. The definition of identity varies as linked classes progress through the linking pipeline, but it only gets stronger, i.e., if two linked classes are id-different at phase P, then they must also be id-different at phase P+1. The converse is not true. This guarantees that versions can be used reliably to determine at phase P+1 whether a linked class coming from phase P must be reprocessed.

4.  abstract class LinkerBackend extends AnyRef

   A backend of a standard Scala.js linker.

   A backend of a standard Scala.js linker.

   Produces a JavaScript file with an optional source map.

   You probably want to use an instance of Linker, rather than this low-level class.

5.  abstract class LinkerFrontend extends AnyRef

   A frontend for a standard Scala.js linker.

   A frontend for a standard Scala.js linker.

   Produces a LinkingUnit.

   You probably want to use an instance of Linker, rather than this low-level class.

   Attention: a LinkerFrontend typically does not cache the IR input. It is advisable to do so, unless all IR is already in memory.

6.  final class LinkingUnit extends AnyRef
7.  sealed trait SymbolRequirement extends AnyRef
8.  final class Versioned[+T] extends AnyRef

   A versioned thing, accompanied by its version.

   A versioned thing, accompanied by its version.

   Note that, as used in LinkingUnit, the version is relative to the identity of the versioned thing. The definition of identity varies as items progress through the linking pipeline, but it only gets stronger, i.e., if two items are id-different at phase P, then they must also be id-different at phase P+1. The converse is not true. This guarantees that versions can be reliably used to determine at phase P+1 whether the given item coming from phase P must be reprocessed.