Usage: kotlinc-js <options> <source files>
where possible options include:
  -libraries <path>          Paths to Kotlin libraries with .meta.js and .kjsm files, separated by system path separator
  -main {call,noCall}        Whether a main function should be called
  -meta-info                 Generate .meta.js and .kjsm files with metadata. Use to create a library
  -module-kind { plain, amd, commonjs, umd }
                             Kind of a module generated by compiler
  -no-stdlib                 Don't use bundled Kotlin stdlib
  -output <path>             Output file path
  -output-postfix <path>     Path to file which will be added to the end of output file
  -output-prefix <path>      Path to file which will be added to the beginning of output file
  -source-map                Generate source map
  -source-map-base-dirs <path> Base directories which are used to calculate relative paths to source files in source map
  -source-map-embed-sources { always, never, inlining }
                             Embed source files into source map
  -source-map-prefix         Prefix for paths in a source map
  -target { v5 }             Generate JS files for specific ECMA version
  -Werror                    Report an error if there are any warnings
  -api-version <version>     Allow to use declarations only from the specified version of bundled libraries
  -X                         Print a synopsis of advanced options
  -help (-h)                 Print a synopsis of standard options
  -kotlin-home <path>        Path to Kotlin compiler home directory, used for runtime libraries discovery
  -language-version <version> Provide source compatibility with specified language version
  -P plugin:<pluginId>:<optionName>=<value>
                             Pass an option to a plugin
  -progressive               Enable progressive compiler mode.
                             In this mode, deprecations and bug fixes for unstable code take effect immediately,
                             instead of going through a graceful migration cycle.
                             Code written in the progressive mode is backward compatible; however, code written in
                             non-progressive mode may cause compilation errors in the progressive mode.
  -nowarn                    Generate no warnings
  -verbose                   Enable verbose logging output
  -version                   Display compiler version
  @<argfile>                 Expand compiler arguments from the given file, containing one argument or file path per line
OK