Release v10.2.0

• Updated TypeScript compiler version and bumped packages.
• Bumped the TypeScript compilation target from es5 to es6 to align with current browser support and reduce the amount of legacy polyfill output in the compiled module.
• Exposed the showBanner, print and printErr callbacks on the Unity Config. These were already supported by the underlying Unity loader but were previously not selectable via useUnityContext. Consumers can now intercept Unity's non-critical warning and error banners (officially supported since Unity 6.3) as well as standard log and error output, and route them into custom UI, telemetry or error reporting instead of relying on the default DOM banner and browser console.
• Added the UnityBannerType type to the public API so consumers can strongly type their showBanner handler without reaching into internal module paths.

Release v10.1.6

• Updated TypeScript compiler version and bumped packages.

Release v10.1.5

• The cleanup canvas element is now hidden by default to prevent display issues in the DOM. This change ensures that the cleanup canvas does not interfere with the layout or visibility of other elements on the page.

Release v10.1.4

• Separated the typings for Untity Message and Unity Event parameters to allow for more granular type checking.

Release v10.1.3

• Resolved an issue where the internal types of the module were not being exported correctly, causing any type in TypeScript projects.

Release v10.1.2

• Replaced the default cache control method with a more robust implementation that handles various scenarios.

Release v10.1.1

• Resolved an issue where not providing a cache control method or webgl context attributes would result in an error while loading the Unity build.

Release v10.1.0

• Added new Unity Metrics Info API and hook to retrieve performance metrics from Unity builds.

Release v10.0.0

• Proud to announce the release of React Unity WebGL version 10.0.0 while celebrating 8 years of React Unity WebGL! This version includes several important updates and fixes, including the removal of the unload function, which is no longer necessary to unmount the Unity Application. The Unity Application will automatically be unmounted when the component is removed from the DOM. However, if you want to unload the Unity Application manually, you can still use the unload function, but be aware that this is not necessary in most cases.

Release v9.9.0

• Added support for configurating autoSyncPersistentDataPath in the Unity configuration.