|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +title: Announcing Scala.js 1.13.1 |
| 4 | +category: news |
| 5 | +tags: [releases] |
| 6 | +permalink: /news/2023/04/10/announcing-scalajs-1.13.1/ |
| 7 | +--- |
| 8 | + |
| 9 | + |
| 10 | +We are pleased to announce the release of Scala.js 1.13.1! |
| 11 | + |
| 12 | +This release mostly contains bug fixes and optimizations. |
| 13 | + |
| 14 | +Read on for more details. |
| 15 | + |
| 16 | +<!--more--> |
| 17 | + |
| 18 | +## Getting started |
| 19 | + |
| 20 | +If you are new to Scala.js, head over to [the tutorial]({{ BASE_PATH }}/tutorial/). |
| 21 | + |
| 22 | +If you need help with anything related to Scala.js, you may find our community [in `#scala-js` on Discord](https://discord.com/invite/scala) and [on Stack Overflow](https://stackoverflow.com/questions/tagged/scala.js). |
| 23 | + |
| 24 | +Bug reports can be filed [on GitHub](https://github.com/scala-js/scala-js/issues). |
| 25 | + |
| 26 | +## Release notes |
| 27 | + |
| 28 | +If upgrading from Scala.js 0.6.x, make sure to read [the release notes of Scala.js 1.0.0]({{ BASE_PATH }}/news/2020/02/25/announcing-scalajs-1.0.0/) first, as they contain a host of important information, including breaking changes. |
| 29 | + |
| 30 | +This is a **patch** release: |
| 31 | + |
| 32 | +* It is backward binary compatible with all earlier versions in the 1.x series: libraries compiled with 1.0.x through 1.13.0 can be used with 1.13.1 without change. |
| 33 | +* It is forward binary compatible with 1.13.0: libraries compiled with 1.13.1 can be used with 1.13.0 without change. |
| 34 | +* It is backward source compatible with 1.13.0: source code that used to compile with 1.13.0 should compile as is when upgrading to 1.13.1. |
| 35 | + |
| 36 | +In addition, like Scala.js 1.13.0: |
| 37 | + |
| 38 | +* It is *not* forward binary compatible with 1.12.x: libraries compiled with 1.13.1 cannot be used with 1.12.x or earlier. |
| 39 | +* It is *not* entirely backward source compatible with 1.12.x: it is not guaranteed that a codebase will compile *as is* when upgrading from 1.12.x or earlier (in particular in the presence of `-Xfatal-warnings`). |
| 40 | + |
| 41 | +As a reminder, libraries compiled with 0.6.x cannot be used with Scala.js 1.x; they must be republished with 1.x first. |
| 42 | + |
| 43 | +## Miscellaneous |
| 44 | + |
| 45 | +### New JDK APIs |
| 46 | + |
| 47 | +This release adds support for the following JDK methods: |
| 48 | + |
| 49 | +* In the classes `java.util.concurrent.atomic.Atomic{Integer,Long,Reference}`, the methods `getAndUpdate`, `updateAndGet`, `getAndAccumulate` and `accumulateAndGet`. |
| 50 | + |
| 51 | +### Optimizations |
| 52 | + |
| 53 | +Scala.js 1.13.1 brings significant improvements to the performance of the linker (the `fastLinkJS` task). |
| 54 | +Most of these improvements apply to incremental scenarios, starting from the second invocation of `fastLinkJS` for a given project in the same build tool session. |
| 55 | +As a result, repeated invocations of `fastLinkJS` (possibly in watch mode, like `~fastLinkJS` in sbt) should feel much snappier than with previous versions. |
| 56 | + |
| 57 | +## Bug fixes |
| 58 | + |
| 59 | +Among others, the following bugs have been fixed in 1.13.1: |
| 60 | + |
| 61 | +* [#4801](https://github.com/scala-js/scala-js/issues/4801) Delegating to the implementation of a calculated super class causes Internal error |
| 62 | +* [#4841](https://github.com/scala-js/scala-js/issues/4841) Repeat calls of `fastLinkJS` sometimes cause `IllegalStateException` on Windows and JDK 17+ |
| 63 | +* [#4833](https://github.com/scala-js/scala-js/issues/4833) High memory consumption during linking when using `ModuleSplitStyle.SmallModulesFor(...)` |
| 64 | +* [#4835](https://github.com/scala-js/scala-js/issues/4835) `SmallModulesFor` splitting style can cause circular dependencies between emitted modules |
| 65 | + |
| 66 | +You can find the full list [on GitHub](https://github.com/scala-js/scala-js/issues?q=is%3Aissue+milestone%3Av1.13.1+is%3Aclosed). |
0 commit comments