Remove nodejs() in wasmJs, use browser() target

[egorikftp]

Breaking change, should be part of 1.5.0

[gemini-code-assist]

Hello @egorikftp, 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!

Summary of Changes

This pull request removes the nodejs() target and replaces it with browser() in the wasmJs configuration for several Gradle build files. This change appears to be a breaking change and is intended to be included in version 1.5.0.

Highlights

• Target Environment: The nodejs() target is replaced with browser() in the wasmJs configuration, indicating a shift in the intended execution environment for the WebAssembly code.
• Breaking Change: The pull request description explicitly marks this change as a breaking change, suggesting potential compatibility issues for existing users.

Changelog

Click here to see the changelog

• example/content/build.gradle.kts
  • Replaced nodejs() with browser() in the wasmJs configuration.
• example/extra/build.gradle.kts
  • Replaced nodejs() with browser() in the wasmJs configuration.
• example/platform/build.gradle.kts
  • Replaced nodejs() with browser() in the wasmJs configuration.
• example/ui-core/build.gradle.kts
  • Replaced nodejs() with browser() in the wasmJs configuration.
• tiamat-koin/build.gradle.kts
  • Replaced nodejs() with browser() in the wasmJs configuration.
• tiamat/build.gradle.kts
  • Replaced nodejs() with browser() in the wasmJs configuration.

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 is currently in preview and 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 to provide feedback.

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.

---

In realms of code, a shift takes place,
Node's reign now yields to browser's grace.
Wasm's spirit, light and free,
Runs where browsers decree.

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

The pull request removes the nodejs() target and replaces it with browser() in the wasmJs configuration for several Gradle build files. This change targets the browser environment for the WebAssembly JavaScript (wasmJs) builds. The change seems straightforward and consistent across all affected files.

Merge Readiness

The pull request appears to be a straightforward change, replacing nodejs() with browser() in the wasmJs configuration. Given the consistency across files and the clear intent, the pull request seems ready for merging. However, since this is a breaking change, ensure that all dependent projects and developers are aware of the change and its implications. I am unable to directly approve the pull request, and users should have others review and approve this code before merging.