Update scalajs-compiler to 1.20.1

[xerial-bot]

About this PR

📦 Updates org.scala-js:scalajs-compiler from 1.19.0 to 1.20.1

📜 GitHub Release Notes - Version Diff

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

🔍 Files still referring to the old version number

The following files still refer to the old version number (1.19.0).
You might want to review and update them manually.

examples/rpc-examples/rpc-scalajs/project/plugins.sbt
examples/rx-demo/gallery/project/plugins.sbt

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "org.scala-js", artifactId = "scalajs-compiler" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-js", artifactId = "scalajs-compiler" }
}]

^{labels: library-update}

[gemini-code-assist]

Summary of Changes

Hello @xerial-bot, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request performs a routine dependency update for the scalajs-compiler library. The primary purpose is to ensure the project utilizes the latest stable version of Scala.js, thereby incorporating recent improvements, bug fixes, and new features from the Scala.js ecosystem. This update helps maintain the project's compatibility and performance with modern web development standards.

Highlights

• Scala.js Compiler Update: The org.scala-js:scalajs-compiler dependency has been updated from version 1.19.0 to 1.20.1.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request updates the Scala.js compiler dependency from version 1.19.0 to 1.20.1. The changes correctly update the version string in the relevant sbt plugin configuration files. The update appears safe as it is a bug-fix release. I have one suggestion to improve long-term maintainability by centralizing the version definition.

[gemini-code-assist]

The SCALAJS_VERSION is also defined in airspec/project/plugin.sbt and sbt-airframe/src/sbt-test/sbt-airframe/js-client/project/plugins.sbt. To follow the DRY (Don't Repeat Yourself) principle and avoid potential version inconsistencies, consider defining this version in a single location. Given the project structure, this could be achieved by reading the version from a properties file at the root of the project in each plugin.sbt file. While Scala Steward handles these updates automatically, centralizing the version would improve manual maintenance in the future.