Skip to content

Commit c80960d

Browse files
Copilotanupriya13
andcommitted
Upgrade website to React Native Windows 0.80
Co-authored-by: anupriya13 <54227869+anupriya13@users.noreply.github.com>
1 parent a99c0b2 commit c80960d

File tree

10 files changed

+1286
-11
lines changed

10 files changed

+1286
-11
lines changed

docs/getting-started.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -25,8 +25,8 @@ Call the following from the place where you want your project directory to live:
2525
<!-- See https://www.npmjs.com/package/@react-native-community/cli?activeTab=versions for the CLI version tags. -->
2626
<!-- See https://www.npmjs.com/package/react-native?activeTab=versions for the RN version tags. -->
2727

28-
```bat
29-
npx --yes @react-native-community/cli@next init <projectName> --version "nightly"
28+
```bat
29+
npx --yes @react-native-community/cli@next init <projectName> --version "nightly"
3030
```
3131

3232
### Navigate into this newly created directory
@@ -50,14 +50,14 @@ Next you'll want to add `react-native-windows` as a dependency:
5050

5151
<!--Using Yarn (Recommended)-->
5252

53-
```bat
54-
yarn add react-native-windows@canary
53+
```bat
54+
yarn add react-native-windows@canary
5555
```
5656

5757
<!--Using NPM-->
5858

59-
```bat
60-
npm install --save react-native-windows@canary
59+
```bat
60+
npm install --save react-native-windows@canary
6161
```
6262

6363
<!--END_DOCUSAURUS_CODE_TABS-->

website/.unbroken_exclusions

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@
1818
!versioned_docs/version-0.77/native-api/*-api-windows*.md
1919
!versioned_docs/version-0.78/native-api/*-api-windows*.md
2020
!versioned_docs/version-0.79/native-api/*-api-windows*.md
21+
!versioned_docs/version-0.80/native-api/*-api-windows*.md
2122

2223
# See Issue 410
2324
File not found IReactContext while parsing versioned_docs/version-0.64/native-modules-advanced.md
@@ -33,6 +34,31 @@ File not found IViewManagerCreateWithProperties while parsing versioned_docs/ver
3334
File not found IViewManagerCreateWithProperties while parsing versioned_docs/version-0.79/view-managers.md
3435

3536
#fix-unbroken.js auto-generated do not edit this line or below
37+
File not found autolink-windows-cli.md while parsing versioned_docs/version-0.80/getting-started.md
38+
File not found getting-started.md while parsing versioned_docs/version-0.80/getting-started.md
39+
File not found init-windows-cli.md while parsing versioned_docs/version-0.80/getting-started.md
40+
File not found native-platform.md while parsing versioned_docs/version-0.80/getting-started.md
41+
File not found new-architecture.md while parsing versioned_docs/version-0.80/getting-started.md
42+
File not found platform.md while parsing versioned_docs/version-0.80/getting-started.md
43+
File not found rnw-dependencies.md while parsing versioned_docs/version-0.80/getting-started.md
44+
File not found run-windows-cli.md while parsing versioned_docs/version-0.80/getting-started.md
45+
File not found run-windows-cli.md while parsing versioned_docs/version-0.80/hermes.md
46+
File not found native-code-language-choice.md while parsing versioned_docs/version-0.80/native-modules.md
47+
File not found native-modules-advanced.md while parsing versioned_docs/version-0.80/native-modules.md
48+
File not found native-modules-async.md while parsing versioned_docs/version-0.80/native-modules.md
49+
File not found native-modules-jsvalue.md while parsing versioned_docs/version-0.80/native-modules.md
50+
File not found native-modules-setup.md while parsing versioned_docs/version-0.80/native-modules.md
51+
File not found native-modules-vs-turbo-modules.md while parsing versioned_docs/version-0.80/native-modules.md
52+
File not found native-platform.md while parsing versioned_docs/version-0.80/native-modules.md
53+
File not found new-architecture.md while parsing versioned_docs/version-0.80/native-modules.md
54+
File not found platform.md while parsing versioned_docs/version-0.80/native-modules.md
55+
File not found view-managers.md while parsing versioned_docs/version-0.80/native-modules.md
56+
File not found getting-started.md while parsing versioned_docs/version-0.80/native-platform-getting-started.md
57+
File not found init-windows-cli.md while parsing versioned_docs/version-0.80/native-platform-getting-started.md
58+
File not found native-platform-components.md while parsing versioned_docs/version-0.80/native-platform-getting-started.md
59+
File not found native-platform-modules.md while parsing versioned_docs/version-0.80/native-platform-getting-started.md
60+
File not found rnw-dependencies.md while parsing versioned_docs/version-0.80/native-platform-getting-started.md
61+
File not found run-windows-cli.md while parsing versioned_docs/version-0.80/native-platform-getting-started.md
3662
File not found new-architecture.md while parsing versioned_docs/version-0.79/app-publishing.md
3763
File not found run-windows-cli.md while parsing versioned_docs/version-0.79/autolink-windows-cli.md
3864
File not found new-architecture.md while parsing versioned_docs/version-0.79/config.md

website/pages/en/support.js

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,14 +14,15 @@ The React Native for Windows (RNW) Team strives to provide full support for the
1414
| Version | Support Phase | Release Date | Active Support Start | Maintenance Support Start | End of Support |
1515
| -- | -- | -- | -- | -- | -- |
1616
| [main](https://www.npmjs.com/package/react-native-windows/v/canary) | [Canary](#canary-support) | *N/A* | *N/A* | *N/A* | *N/A* |
17-
| [0.79](https://www.npmjs.com/package/react-native-windows/v/latest) | [Active](#active-support) | 06/17/2025 | 06/17/2025 | *TBD* | *TBD* |
18-
| [0.78](https://www.npmjs.com/package/react-native-windows/v/v0.78-stable) | [Active](#active-support) | 02/27/2025 | 02/27/2025 | 07/31/2025 | 09/30/2025 |
17+
| [0.80](https://www.npmjs.com/package/react-native-windows/v/latest) | [Active](#active-support) | 12/16/2025 | 12/16/2025 | *TBD* | *TBD* |
18+
| [0.79](https://www.npmjs.com/package/react-native-windows/v/v0.79-stable) | [Active](#active-support) | 06/17/2025 | 06/17/2025 | 01/31/2026 | 03/31/2026 |
19+
| [0.78](https://www.npmjs.com/package/react-native-windows/v/v0.78-stable) | [Unsupported](#unsupported) | 02/27/2025 | 02/27/2025 | 07/31/2025 | 09/30/2025 |
1920
| [0.77](https://www.npmjs.com/package/react-native-windows/v/v0.77-stable) | [Unsupported](#unsupported) | 01/24/2025 | 01/24/2025 | 03/27/2025 | 05/31/2025 |
20-
| [0.76](https://www.npmjs.com/package/react-native-windows/v/v0.76-stable) | [Unsupported](#unsupported) | 11/11/2024 | 11/11/2024 | 02/28/2025 | 04/30/2025 |
21-
| [0.75](https://www.npmjs.com/package/react-native-windows/v/v0.75-stable) | [Unsupported](#unsupported) | 8/19/2024 | 8/19/2024 | 12/31/2024 | 02/28/2025 |
2221
2322
<!--
2423
// We don't want the table to grow indefinitely, so only keep the last 5 stable (non-main) versions visible above, keep the rest here for posterity.
24+
| [0.76](https://www.npmjs.com/package/react-native-windows/v/v0.76-stable) | [Unsupported](#unsupported) | 11/11/2024 | 11/11/2024 | 02/28/2025 | 04/30/2025 |
25+
| [0.75](https://www.npmjs.com/package/react-native-windows/v/v0.75-stable) | [Unsupported](#unsupported) | 8/19/2024 | 8/19/2024 | 12/31/2024 | 02/28/2025 |
2526
| [0.74](https://www.npmjs.com/package/react-native-windows/v/v0.74-stable) | [Unsupported](#unsupported) | 4/29/2024 | 4/29/2024 | 9/30/2024 | 11/30/2024 |
2627
| [0.73](https://www.npmjs.com/package/react-native-windows/v/v0.73-stable) | [Unsupported](#unsupported) | 12/11/2023 | 12/11/2023 | 5/31/2024 | 7/31/2024 |
2728
| [0.72](https://www.npmjs.com/package/react-native-windows/v/v0.72-stable) | [Unsupported](#unsupported) | 06/23/2023 | 06/23/2023 | 01/31/2024 | 03/31/2024 |

website/siteConfig.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
// See https://docusaurus.io/docs/site-config for all the possible
99
// site configuration options.
1010

11-
const defaultVersionShown = "0.79";
11+
const defaultVersionShown = "0.80";
1212
const repoUrl = "https://github.com/microsoft/react-native-windows";
1313

1414
const siteConfig = {
Lines changed: 138 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,138 @@
1+
---
2+
id: version-0.80-getting-started
3+
title: Get Started with Windows
4+
original_id: getting-started
5+
---
6+
7+
![Architecture](https://img.shields.io/badge/architecture-new_&_old-green)
8+
9+
This guide will help you get started on setting up your very first React Native for Windows app.
10+
11+
Make sure you have installed all of the [development dependencies](rnw-dependencies.md).
12+
13+
For information around how to set up React Native, see the [React Native Getting Started Guide](https://reactnative.dev/docs/getting-started).
14+
15+
> **Interested in migrating to [React Native's New Architecture](https://reactnative.dev/architecture/landing-page)?** New Architecture support in React Native for Windows is now available to preview in 0.76. Note there are several key changes, so if you’d like to be an early adopter, check out the information in the [New Architecture Guide](new-architecture.md).
16+
17+
## Create a new React Native project
18+
19+
Call the following from the place where you want your project directory to live:
20+
21+
<!-- Note, make sure both `@react-native-community/cli@ABC` and `--version "XYZ"` are pointing to the correct NPM tags in the command below. -->
22+
23+
<!-- 1. For the next version (i.e. in docs/getting-started.md) use "next" for the CLI and "nightly" for the RN version -->
24+
<!-- 2. For stable versions in versioned_docs use "latest" for the CLI and the semantic version, i.e. "^0.73.0" for the RN version -->
25+
26+
<!-- See https://www.npmjs.com/package/@react-native-community/cli?activeTab=versions for the CLI version tags. -->
27+
<!-- See https://www.npmjs.com/package/react-native?activeTab=versions for the RN version tags. -->
28+
29+
```bat
30+
npx --yes @react-native-community/cli@latest init <projectName> --version "^0.80.0"
31+
```
32+
33+
### Navigate into this newly created directory
34+
35+
The command will create your project in a new sub-directory, which you must enter before continuing:
36+
37+
```bat
38+
cd <projectName>
39+
```
40+
41+
### Add React Native Windows to your project's dependencies
42+
43+
<!-- Note, make sure "version" is pointing to the correct react-native-windows NPM tag in the command below. -->
44+
45+
<!-- 1. For the next version (i.e. in docs/getting-started.md) use "canary" -->
46+
<!-- 2. For other versions in versioned_docs use the version in the format "^0.XY.0" -->
47+
48+
Next you'll want to add `react-native-windows` as a dependency:
49+
50+
<!--DOCUSAURUS_CODE_TABS-->
51+
52+
<!--Using Yarn (Recommended)-->
53+
54+
```bat
55+
yarn add react-native-windows@^0.80.0
56+
```
57+
58+
<!--Using NPM-->
59+
60+
```bat
61+
npm install --save react-native-windows@^0.80.0
62+
```
63+
64+
<!--END_DOCUSAURUS_CODE_TABS-->
65+
66+
### Initialize the React Native Windows native code and projects
67+
68+
Lastly, initialize the React Native for Windows application with the [init-windows command](init-windows-cli.md):
69+
70+
```bat
71+
npx react-native init-windows --overwrite
72+
```
73+
74+
> **Note:** RNW templates contain a customized `metro.config.js` file, which is meant to merge cleanly into the default config provided by the standard React Native project template. If you are starting a new app, overwriting `metro.config.js` should have no impact. However, if you are adding Windows to an existing app with an already modified `metro.config.js` file, please make sure to back up and re-apply your modifications after adding RNW.
75+
76+
## Running a React Native Windows App
77+
78+
> Make sure a browser is launched and running before running a React Native Windows app.
79+
> Also ensure your system meets all the [requirements](rnw-dependencies.md) to build a Windows app as well.
80+
81+
- Without Using Visual Studio
82+
83+
In your React Native Windows project directory, run the [run-windows command](run-windows-cli.md):
84+
85+
```bat
86+
npx react-native run-windows
87+
```
88+
89+
A new Command Prompt window will open with the React packager as well as your React Native for Windows app. This step may take a while during first run since it involves building the entire project and all dependencies. You can now start developing! :tada:
90+
91+
- Using Visual Studio
92+
93+
- From the root of the project directory, run the [autolink-windows command](autolink-windows-cli.md), which will automatically link your app's dependencies:
94+
```bat
95+
npx react-native autolink-windows
96+
```
97+
- Open the solution file in the application folder in Visual Studio (e.g., `AwesomeProject/windows/AwesomeProject.sln` if you used `AwesomeProject` as `<projectName>`)
98+
- Select the `Debug` configuration and the `x64` platform from the combo box controls to the left of the `Run` button and underneath the `Team` and `Tools` menu item.
99+
- Run `yarn start` (or `npm start`) from your project directory, and wait for the React Native packager to report success.
100+
- Click the `Run` button to the right of the platform combo box control in VS, or select the `Debug`->`Start without Debugging` menu item. You now see your new app and Chrome should have loaded `http://localhost:8081/debugger-ui/` in a new tab. Press `F12` or `Ctrl+Shift+I` in Chrome to open its Developer Tools. :tada:
101+
102+
- With VS Code
103+
- Open your applications folder in VS Code.
104+
- Install the [React Native Tools](https://marketplace.visualstudio.com/items?itemName=msjsdiag.vscode-react-native) plugin for VS Code.
105+
- Create a new file in the applications root directory, `.vscode/launch.json` and paste the following configuration:
106+
```json
107+
{
108+
"version": "0.2.0",
109+
"configurations": [
110+
{
111+
"name": "Debug Windows",
112+
"cwd": "${workspaceFolder}",
113+
"type": "reactnative",
114+
"request": "launch",
115+
"platform": "windows"
116+
}
117+
]
118+
}
119+
```
120+
- Press `F5` or navigate to the debug menu (alternatively press `Ctrl+Shift+D`) and in the Debug drop-down select "Debug Windows" and press the green arrow to run the application.
121+
122+
## Authoring Native Modules
123+
124+
See [Native Platform: Overview](native-platform.md).
125+
126+
## Building a standalone React Native Windows App
127+
128+
Follow these steps to build a version of your app that you can install or publish to the store. This version will package your bundle and assets into the APPX package so you don't need to run Metro.
129+
130+
- Open the solution in Visual Studio
131+
- Select the Release configuration from the Configuration Manager drop-down.
132+
- Build the solution. You can now launch without first launching Metro.
133+
- If you want to build an APPX package to share or publish, use the **Project** > **Publish** > **Create App Packages...** option.
134+
135+
> The Debug configuration uses the Web Debugger by default, which means the application's JavaScript code runs in Chrome.<br>
136+
> If you're getting different runtime behavior between the Release and Debug configurations, consider disabling the `UseWebDebugger` setting in [`App.cpp`](https://github.com/microsoft/react-native-windows/blob/6b415659aa017dbc41e3f28e817fb768a8e80435/vnext/template/cpp-app/src/App.cpp#L30) or [`App.xaml.cs`](https://github.com/microsoft/react-native-windows/blob/6b415659aa017dbc41e3f28e817fb768a8e80435/vnext/template/cs-app/src/App.xaml.cs#L20) to get the same behavior in the Debug configuration.
137+
138+
See also this article for additional details: https://techcommunity.microsoft.com/t5/windows-dev-appconsult/getting-started-with-react-native-for-windows/ba-p/912093#
Lines changed: 102 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,102 @@
1+
---
2+
id: version-0.80-hermes
3+
title: Hermes on Windows
4+
original_id: hermes
5+
---
6+
7+
![Architecture](https://img.shields.io/badge/architecture-new_&_old-green)
8+
9+
# Hermes
10+
11+
The [Hermes](https://hermesengine.dev/) engine is an open source JavaScript engine created by Facebook to optimize building and running React Native applications.
12+
13+
To learn more about what it is and how to use it, check out the [React Native](https://reactnative.dev/docs/hermes#docsNav) documentation for it.
14+
15+
## Hermes on Windows:
16+
17+
Hermes is supported on Windows, generally providing better performance characteristics than the default Chakra engine.
18+
19+
### Enabling Hermes for new projects
20+
21+
Hermes is enabled by default for React Native Windows projects.
22+
23+
### Using Hermes in an existing project
24+
25+
Set the `UseHermes` property to `true` in the `ExperimentalFeatures.props` file in your project's `windows` directory:
26+
27+
```xml
28+
<PropertyGroup Label="Microsoft.ReactNative Experimental Features">
29+
...
30+
<UseHermes>true</UseHermes>
31+
</PropertyGroup>
32+
```
33+
34+
### Disabling Hermes
35+
36+
To revert back to using Chakra, set the `UseHermes` property to `false` in the `ExperimentalFeatures.props` file in your project's `windows` directory:
37+
38+
```xml
39+
<PropertyGroup Label="Microsoft.ReactNative Experimental Features">
40+
...
41+
<UseHermes>false</UseHermes>
42+
</PropertyGroup>
43+
```
44+
45+
### Known limitations
46+
47+
- Hermes dll is not signed by Microsoft.
48+
49+
## Hermes Inspector
50+
51+
*React Native for Windows* with *Hermes engine* supports direct JavaScript runtime inspection using tools such as Chrome or [Edge `devtools`](https://docs.microsoft.com/microsoft-edge/devtools-guide-chromium/), [`VSCode` debugger](https://code.visualstudio.com/Docs/editor/debugging), [Flipper](https://fbflipper.com/) etc. by implementing an in-process Chrome Debug Protocol server.
52+
Please note that it is fundamentally different from "Remote JS Debugging", which loads the JavaScript bundle into a remote Chrome browser session with duplex communication over IPC channels.
53+
54+
We share the implementation (code and design) with other platforms wherever possible. All the external endpoints, APIs and protocols should be identical to *React Native* environments on other platforms.
55+
Hence, we expect most tooling available on other platforms to just work on Windows. But, as of now, we have tested only with Chrome and Edge `devtools`.
56+
57+
### Steps to enable direct debugging
58+
59+
1. Initialize React Native Host,
60+
- Turn on `DeveloperSupport`
61+
- Turn on `FastRefresh`
62+
- Turn off `WebDebugger`
63+
- Turn on `Direct Debugging`
64+
2. Ensure Dev-Server is running
65+
3. Start the application
66+
67+
After the app has booted,
68+
69+
4. Navigate to `edge://inspect` in Edge browser or `chrome://inspect` in Chrome browser
70+
5. Enable **Discover network targets** and **configure** the target discovery settings to include `localhost:8081` (or wherever the metro server is running)
71+
6. Within a few seconds "Hermes React Native" should appear on the page as a remote target
72+
7. Click on the **inspect** link to launch the `devtools` page
73+
8. Click `Ctrl+P` to open source files and set break points
74+
9. Alternatively, you can insert `debugger` statements in source code to break on specific locations
75+
76+
In order to break on locations during boot, you can either
77+
78+
- Add statements into the boot sequence to pause the runtime waiting for debugger to connect.
79+
```js
80+
debugger;
81+
```
82+
- Set a break point and refresh the bundle through the Dev Server. The runtime will wait for debugger to attach.
83+
84+
85+
### Steps to enable heap profiling
86+
87+
Follow steps 1-7 from above, and then
88+
1. Click on the "Memory" tab in the inspector
89+
2. Heap snapshots and instrumented allocations should be working.
90+
91+
### Enable debugging/profiling on release builds
92+
93+
We keep the inspector turned off on release builds by default. If you want to debug or profile release builds, set the MSBuild property `EnableHermesInspectorInReleaseFlavor` to `'true'` when building the platform with the [run-windows command](run-windows-cli.md), i.e.:
94+
95+
```bash
96+
npx react-native run-windows --msbuildprops EnableHermesInspectorInReleaseFlavor=true
97+
```
98+
99+
### Known Issues
100+
101+
1. CPU Sampling profiler currently doesn't work.
102+

0 commit comments

Comments
 (0)