Announcing Scala.js 1.3.0. #518
Conversation
sjrd force-pushed the scalajs-1.3.0 branch 3 times, most recently from 4a4096d to 3a6ad56 Compare 
| scalaJSLinkerConfig ~= (_.withModuleSplitStyle(ModuleSplitStyle.SmallestModules)) | ||
| {% endhighlight %} | ||
| | ||
| #### For different entry points |
There was a problem hiding this comment.
IMO this should come first. That use case is entirely usefully satisfied by Scala.js core. The "many small modules" use case is useful only when piped through a bundler down the line.
| | ||
| #### For different entry points | ||
| | ||
| Set the `moduleID` for your top level exports and/or module initializers explicitly. |
There was a problem hiding this comment.
Perhaps we should add
| Set the `moduleID` for your top level exports and/or module initializers explicitly. | |
| Set the `moduleID` for your top level exports and/or module initializers explicitly (a module initializer is basically a main method for the module). |
There was a problem hiding this comment.
Also I think we spell "top-level exports" with a dash in "top-level", don't we?
| | ||
| ### Entry Points | ||
| | ||
| Scala.js generated code has two different kinds of entry points: |
There was a problem hiding this comment.
I believe this should be spelled "Scala.js-generated code", with a dash, shouldn't it?
| Scala.js generated code has two different kinds of entry points: | ||
| | ||
| * Top level exports: Definitions to be called from external JS code. | ||
| * Module initializers: Code that gets executed when a module is imported. |
There was a problem hiding this comment.
| * Module initializers: Code that gets executed when a module is imported. | |
| * Module initializers: Code that gets executed when a module is imported (i.e., main methods). |
?
| | ||
| This also works for more than two public modules, creating intermediate shared (internal) modules as necessary. | ||
| | ||
| #### `SmallestModules` |
There was a problem hiding this comment.
It might be good to add a sentence saying why this can be useful? (i.e., to speed up incremental bundling if the output is fed to downstream tooling)
| Yes to all your comments. I'll review the rest tomorrow morning. |
| We are excited to announce the release of Scala.js 1.3.0! | ||
| | ||
| This release brings one of the most awaited features for Scala.js: module splitting support! | ||
| It is now possible to split the generated .js file in multiple modules, to optimize download size in multi-page applications or speed up incremental bundling. |
| | ||
| * [#4195](https://github.com/scala-js/scala-js/issues/4195) `LinkedHashMap` iteration not empty after `clear` | ||
| * [#4188](https://github.com/scala-js/scala-js/issues/4188) Make `js.Promise.then` return `js.Promise` instead of `js.Thenable` | ||
| * [#4203](https://github.com/scala-js/scala-js/issues/4203) `Matcher.region not mutating the matcher |
There was a problem hiding this comment.
There is an escaping problem here.
| | ||
| New interface definitions in `java.util.function.*`: | ||
| | ||
| * `Consumer`, `BiConsumer`, `Supplier`, `Function`, `BiFunction`, `UnaryOperator`, `BinaryOperator` and `BiPredicate` |
There was a problem hiding this comment.
Consumer has been present in v0.6.32 / v.1.0.0: scala-js/scala-js@7fd9ebb
| Among others, the following bugs have been fixed in 1.3.0: | ||
| | ||
| * [#4195](https://github.com/scala-js/scala-js/issues/4195) `LinkedHashMap` iteration not empty after `clear` | ||
| * [#4188](https://github.com/scala-js/scala-js/issues/4188) Make `js.Promise.then` return `js.Promise` instead of `js.Thenable` |
There was a problem hiding this comment.
This is a potentially source incompatible change. Shall we point this out?
| Thanks for the review. I've added two commits, one addressing my review and one addressing yours. If LGTY I'll squash everything together before merging. |
| {% endhighlight %} | ||
| First, instead of `fastOptJS` / `fullOptJS`, use `fastLinkJS` / `fullLinkJS`. | ||
| The outputs of those commands will be in a subdirectory like `project/target/scala-2.13/project-fastopt/`, instead of as a single file `.../scala-2.13/project-fastopt.js`. | ||
| You can then create different entry points or generate as many small modules as possible using the following setups. |
There was a problem hiding this comment.
"and/or" to make it clear these compose?
| * many internal small modules (~50 for this example), approximately one per class. | ||
| | ||
| Generating many small modules can be useful if the output of Scala.js is further processed by downstream JavaScript bundling tools. | ||
| In incremental builds, they will not need to reparse the entire Scala.js-generated .js file, but instead only the small modules that have changed. |
| | ||
| The result type of `js.Promise.then` was changed from `js.Thenable` to `js.Promise`. | ||
| This is unlikely to cause any issue in most cases, since `js.Promise` extends `js.Thenable`. | ||
| It might cause compilation error in some rare cases due to type inference, or if you declare a subclass of `js.Promise`. |
Co-authored-by: Tobias Schlatter <tobias@meisch.ch>
Fixed and squashed :) |
2 participants
No description provided.