Not a developer? Check out the command line tool instead.
In batch mode the converter will process all files from the DefinitelyTyped project, as well as a selection of libraries from npm.
You can run the main
directly from from sbt (
importer/run) or intellij. Since it's used both for development and for CI,
it supports a bunch of command line options.
All parameters without a leading dash will be taken to be names of libraries to convert.
Specifying one or more libraries will put the converter in "debug mode". The only difference is that the UI is different, and no sbt plugin and commit is created. For development you'll always use "debug mode".
Main supports a bunch of command line options:
|The CI server (and perhaps your developer laptop) doesn't have much hard drive space. This thins out the |
|Adds the set of all libraries used in the demos|
|Normally the CI build aggressively resets the ScalablyTyped git repo. Enabling this will skip that|
|The Typescript parser is somewhat slow. Enabling this uses java serialization to cache when possible|
|Commit and build sbt plugin in debug mode|
|Build libraries with Scala 2.12 instead of 3.0.0|
|Build libraries with Scala 2.13 instead of 3.0.0|
|Skip pulling newest DefinitelyTyped and running |
|Make the converter more strict. Most things don't work yet in this mode|
|Will only write changed/deleted files. This is essential if you want to keep ScalablyTyped products open in an IDE to avoid reindexing the world.|
|Use slinky flavour, integrate with scala-js-dom, and generate slinky components|
|Use scalajs-react flavour, integrate with scala-js-dom, and generate scalajs-react components|
|Rewrite types to use scala-js-dom types when using |
|Run a benchmark run. Typically use with |
By default, all files will be written to
~/.cache/scalablytyped. The only exception is the ivy artifacts, which are local-published