Fix casemapping on web

[mosuem]

Due to some JS interop change.

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[gemini-code-assist]

Summary of Changes

Hello @mosuem, 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 addresses a critical casemapping bug affecting the intl4x package on the web, which arose due to recent JavaScript interop modifications. The changes include a fix for this behavior, updates to package versions and SDK constraints, and a refinement of the JavaScript interop declarations for string case conversion methods.

Highlights

• Web Casemapping Fix: Corrected an issue with casemapping functionality on the web platform, likely stemming from recent JavaScript interop changes.
• Dependency and SDK Updates: The intl4x package and its example project had their Dart SDK constraints and several dependencies updated to newer versions.
• JS Interop Refinement: Explicit @JS annotations were removed from toLocaleUpperCase and toLocaleLowerCase methods in the JSString extension, streamlining JavaScript interop declarations.

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 by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

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 pull request 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. ↩

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:intl	0.20.3-wip	WIP (no publish necessary)
package:intl4x	0.13.1	ready to publish	intl4x-v0.13.1
package:intl_translation	0.21.0	already published at pub.dev
package:messages_shrinker	0.2.2-wip	WIP (no publish necessary)

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[gemini-code-assist]

Code Review

This pull request effectively fixes case mapping on the web by removing incorrect @JS annotations in case_mapping_ecma.dart. This change, prompted by an update in JS interop behavior, simplifies the code and improves maintainability. The accompanying version bumps for the package, SDK, and dependencies are appropriate for this fix, and the changelog has been updated accordingly. The changes are correct and well-contained. The PR looks good to merge.

[github-actions]

PR Health

Breaking changes ✔️

Package	Change	Current Version	New Version	Needed Version	Looking good?
intl4x	Non-Breaking	0.13.0	0.13.1	0.13.1	✔️

This check can be disabled by tagging the PR with skip-breaking-check.

Changelog Entry ✔️

Package	Changed Files

Changes to files need to be accounted for in their respective changelogs.

This check can be disabled by tagging the PR with skip-changelog-check.

Coverage ⚠️

File	Coverage
pkgs/intl4x/lib/src/case_mapping/case_mapping_ecma.dart	💔 Not covered

This check for test coverage is informational (issues shown here will not fail the PR).

This check can be disabled by tagging the PR with skip-coverage-check.

API leaks ✔️

The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.

Package	Leaked API symbol	Leaking sources

This check can be disabled by tagging the PR with skip-leaking-check.

License Headers ✔️

// Copyright (c) 2025, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

This check can be disabled by tagging the PR with skip-license-check.

[robertbastian]

sure