react-native-windows

This is patch release of react-native-windows, fixing bugs or adding non-breaking enhancements. To see a summary of changes in this major release, see release notes for React Native Windows 0.63.0.

New changes

• 4026d6ba Allow propagating WinRTWebSocketResource constructor exceptions (#7892) ([email protected])
• bc22bbc0 Try to work around new nuget braking change ([email protected])
• 1575e0a8 V8 package update ([email protected])
• 4567dace Add JSI.MemoryMappedScriptStore runtime option to control usage of MemoryMappedBuffer (#7943) ([email protected])
• e5df6cce Fix JSValue memory leak in move constructor ([email protected])

This is patch release of react-native-windows, fixing bugs or adding non-breaking enhancements. To see a summary of changes in this major release, see release notes for React Native Windows 0.64.0.

New changes

• 440f6943 Fix Text.BackgroundColor overwriting foreground. (#7707) ([email protected])
• fb0db424 Add error message when an exception happens in a native module (in Debug) ([email protected])
• 3bfe8e15 Fix JSValue memory leak in move constructor ([email protected])
• 8209eb53 Update .net uwp package version ([email protected])

We're excited to release our first preview build of react-native-windows 0.65! There have been many changes to both react-native-windows and react-native itself and we would love your feedback on anything that doesn't work as expected.

What's New

• Hermes debugging and profiling: You can now debug and profile the heap-usage of your JavaScript code running on Hermes. See this document for details.

• New component capabilities: We've added Windows support for some existing, and some all new properties, including:

  • <Button>: tabIndex
  • <Pressable>: onKeyDown/onKeyUp
  • <TextInput>: autoFocus, clearTextOnSubmit, submitKeyEvents
  • <Image>: SVG data URI in source

• TraceLogging based ETW events: We now expose the ability to record ETW events for various framework actions. See Event Tracing in React Native for Windows for details.

• Hermes 0.8.0 with Improved Garbage Collector: Hermes 0.8.0 introduces The Hades Garbage Collector, which dramatically reduces GC pause times.

• More consistent styling for <Button>: The stock <Button> component has been updated with a look-and-feel consistent with other Windows controls.

• WinUI 2.5: We upgraded from WinUI 2.3 to WinUI 2.5, offering more refined native controls.

• FlatList performance improvements: Several performance issues causing excessive renders when using FlatList have been fixed.

• Opt-in fast builds: Set the RNW_FASTBUILD environment variable to true to enables building with larger PCH's. This leads to a much faster build, at the expense of higher system requirements to build successfully.

• IViewManagerCreateWithProperties: View managers may implement IViewManagerCreateWithProperties to receive properties at the time of view creation, simplifying cases where different properties may lead to different native views.

• Bug-fixes and improvements: The above just scratches the surface of the work that has been happening! We've been continually making bug fixes and improvements across the project.

Breaking Changes

• Legacy WebSocket implementation: We introduced a new WebSocket stack in 0.64, along with the QuirkSettings::SetUseLegacyWebSocketModule function to opt-out of it. This setting is now removed, and the new implementation is always used.

• 32-bit ARM support: We removed support for 32-bit ARM processors, which are used on some Windows IoT Core devices.

• WinUI 3 Islands: React Native Windows now targets WinUI 3 preview 4 when set to use WinUI 3. This requires changes for applications using WinUI 3 with XAML Islands.

How to upgrade

We've made it easier to upgrade to newer versions of react-native-windows!

While we are working to bring Windows support to React Native Upgrade Helper, you can see a diff explaining how to update your project using https://github.com/acoates-ms/rnw-diff. The below example shows the comparison between 0.63.0 and 0.64.0-preview.1:

During the preview period of 0.65 you will have to declare a dependency on [email protected] in your package.json file. When we release, this version will be replaced with react-native@^0.65.

...
"dependencies":  {
  "react-native": "0.0.0-7e05480cc"
}
...

This is patch release of react-native-windows, fixing bugs or adding non-breaking enhancements. To see a summary of changes in this major release, see release notes for React Native Windows 0.63.0.

New changes

• 3a771348 Update .net uwp version ([email protected])

This is patch release of react-native-windows, fixing bugs or adding non-breaking enhancements. To see a summary of changes in this major release, see release notes for React Native Windows 0.64.0.

New changes

• 061fc642 Fix MSBuild Bundling When Path Contains Spaces ([email protected])
• 8e1ef742 [0.64] Fix transitive dependencies for C# nuget-based apps #7786 ([email protected])

• 7734d7bf [0.64] Upgrade JSI.Desktop projects version of ChakraCore ([email protected])
• d00548f5 Use memory-mapping in BasePreparedScriptStoreImpl::tryGetPreparedScript ([email protected])
• 269861da Update brush cache when theme changes ([email protected])

• bc33b309 Use memory-mapping in BasePreparedScriptStoreImpl::tryGetPreparedScript ([email protected])

• cf58dd63 Update V8 package version ([email protected])

• 82f12b42 If initial value is set, updated TextInput.value changes will not be reflected ([email protected])
• 04b40043 [0.64] Update Microsoft.ChakraCore to 1.11.24 (#7628) ([email protected])
• e7efb402 Initialize ETW provider only once ([email protected])
• e7efb402 Last year, we had plumbed the Systrace sections and events in the core react native to windows code and fired ETW events. But, it was hard for people to use because we used manifest based ETW events. This change converts the event triggering code to use Tracelogging APIs (aka self describing events) which doesn't require the manifest to be registered on the host machine to inspect traces.
  Post this change, the systrace events can be inspected on any windows machines where the RNW based apps are running by issuing the following commands,
  wpr.exe -start rnw.wprp
  wpr.exe -stop rnw.etl
  wpa.exe rnw.etl

This works for Win32 apps too, say Office. ([email protected])

• 4b552ca0 Remove version from ExperimentalFeatures.props links ([email protected])

• a29cccfa Suppress onLayout event when layout has not changed (#7470) ([email protected])
• 51feac94 Change TextInput cursor behavior (#7285) ([email protected])

• 09ac2fd1 Enable any platform color to be used in PlatformColor() ([email protected])
• ebf82d62 Calling UIManager.dispatchViewManagerCommand should trigger updates ([email protected])
• d731a4f1 Allow swapping to System Chakra at runtime. ([email protected])

• cb3d8109 Allow swapping to System Chakra at runtime. ([email protected])

• e5077c3d Add doc comments to IDL files ([email protected])
• e5077c3d Fix some doc typos, generate docs in CI ([email protected])
• d55a22fb [0.64] Enable apps to override WinUI and SDK version for RNW framework projects ([email protected])

• 0437f2f3 [0.64] Update cppwinrt package version ([email protected])
• eb8daf4e Fix template for WinUI3 C# App by expanding namespace of argument in AppOnActivated ([email protected])
• eb8daf4e Fix deep linking activation ([email protected])
• 9208f85c Make BaseWebSocketResource destructor noexcept ([email protected])
• 1615a243 [0.64] AzDO image now installs uwp package 6.2.11, not 6.2.10; Update Codegen UnitTest ([email protected])
• 459f3504 Fix DevMenuControl.xbf copy conflict ([email protected])
• 252afeb9 Improve Microsoft.ReactNative compilation speed ([email protected])

• dd05bb44 [0.64] Fix app template to use app.json's name for main component name (#7464) ([email protected])
• 1d1bb1b9 [0.64] Implement JSI getOwnPropertyDescriptor ([email protected])
• c7637b30 Bump peer dependency to require non-rc version of react-native ([email protected])

• 79cdd5cb Debugging: Adding variables to watch window crashes the process hosting the addin VSO 4853697 ([email protected])

• 6a5dab58 Fix AppStateModule::GetCurrentAppState from returning undefined ([email protected])
• bbd6a0a2 Backporting codegen test fix for build on new agents ([email protected])
• db69246d Promote 0.63 to legacy ([email protected])

We're excited to release React Native Windows 0.64.0, targeting React Native 0.64.0. There have been more new features, bugfixes, and enhancements than we can count, with some of the significant ones listed below.

Getting Started documentation here
Release notes for React Native 0.64 here

What's new

• Easy opt-in to Hermes: It's easier than ever to try Hermes! We expect projects trying Hermes to see performance increases in most cases. While there are teams using Hermes in production, its support is still experimental, and we do not yet support Hermes debugger or Hermes in C# applications. We would still love to know if you try Hermes and run into any issues.

• Improved API parity: More component properties supported by other platforms now work on Windows, such as Text backgroundColor, border, and textTransform. An initial version of AccessibilityInfo is now available. Platform.version is now implemented.

• React 17 and faster startup by default: React Native 0.64 brings the latest version of React, and changes the default metro configuration to enable "inline requires", allowing for faster startup by default.

• Community module templates: A new workflow makes it easier to create community modules for Windows by using a built-in template.

• Instance lifecycle events: Native code can now respond to the react native instance being created, loaded, or destroyed.

• A brand new WebSocket stack: The existing WebSocket stack has been replaced with an all new, more-correct, production-hardened implementation.

• Bug-fixes and improvements: The above just scratches the surface on the work that has been happening! We've been continually making bug fixes and improvements across the project.

Experimental Features

• Access to the JSI runtime: C++ applications can now directly interface with the JSI runtime using the winrt::Microsoft::ReactNative::ExecuteJSI API. This will work anywhere a ReactContext is available and web-debugging is not in use.

• TurboModule compatibility: Existing C++ TurboModules can be used with react-native-windows. Code generation is not yet exposed.

Deprecations

• 32-bit ARM is deprecated: Some Windows IoT Core devices run 32-bit ARM processors. These devices are rare, and have not been tested with react-native-windows. We will be removing support for ARM32 in a future release. ARM64 remains supported.

Breaking Changes

• Native module thread affinity: A bug was discovered which led to custom native modules often being invoked on the UI thread. This was unintentional and has been changed. We recognize that this may break existing modules in cases where affinity was relied upon without explicitly queuing to the UI thread. Please let us know if you run into broken community modules.

• acceptsKeyboardFocus is removed: In 0.63 we started warning on usage of acceptsKeyboardFocus that the property would be replaced by the built-in and type-safe focusable. In 0.64 we removed support from the property, redboxing if it is passed to a view and ignoring the property on touchables.

• AppTheme API reconciliation with Appearance: React Native 0.62 introduced Appearance and useColorScheme hooks to respond to changes in light/dark mode. This functionality supersedes several APIs in the react-native-windows specific AppTheme library. AppTheme functions that warned about removal in 0.63 are removed in 0.64. See more here on how to write components that adapt to theme.

• Setting accessibility props no longer makes controls focusable: Previous behavior made any view focusable with accessibility properties set. This is often not the desired effect, and focusable now controls this.

• EmitJSEvent parameter passing: Calls to EmitJSEvent on the ReactContext previously wrapped the event object in a JavaScript array instead of passing it 1:1. This was fixed in 0.64, but any existing consumption of events fired by EmitJSEvent must be updated.

• ref.focus() focus visuals: Calling focus() on a component ref will now show native focus visuals by default. If you don't want focus visuals around your component, you can set the property enableFocusRing={false}.

• Synchronous native module returns: Native module methods marked as synchronous would previously have their results wrapped in an array. This is no longer the case.

Upgrading

The most surefire way to upgrade from 0.62 or 0.63 is to generate a new project targeting 0.64 using react-native-windows-init and copy over your project content. In the future we would like to provide diffs to help make this easier in the style of react-native-upgrade-helper.

• ebb968fc beachball sync ([email protected])
• dc74c798 [0.64] Port IJSValueWriter/IJSValueReader docs from master ([email protected])
• 7b4bb634 [0.64] Enabling codesigning via ESRP ([email protected])
• 5d7ed092 Raise Instance notifications in JSDispatcher thread ([email protected])
• 2f2b0788 Disable warning 4103 in MemoryMappedBufferTests.cpp (#7319) ([email protected])
• f901b5ff [0.64] Fix usage of std::thread in RN's RuntimeExecutor ([email protected])
• 3a3f0bd6 Fix right click warning. ([email protected])
• c73bb3ae Remove unnecessary exceptions to unblock some partners ([email protected])
• bfebc673 Clarify IJSValueWriter/IJSValueReader docs ([email protected])