You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ We want this community to be friendly and respectful to each other. Please follo
8
8
9
9
This project is a monorepo managed using [Yarn workspaces](https://yarnpkg.com/features/workspaces). It contains the following packages:
10
10
11
-
- The library package in `packages/react-native-release-inspector`.
11
+
- The library package in `packages/inspector`.
12
12
- An example app in `apps/example`.
13
13
14
14
To get started with the project, make sure you have the correct version of [Node.js](https://nodejs.org/) installed. See the [`.nvmrc`](./.nvmrc) file for the version used in this project.
@@ -25,9 +25,9 @@ The [example app](/apps/example/) demonstrates usage of the library. You need to
25
25
26
26
It is configured to use the local version of the library, so any changes you make to the library's source code will be reflected in the example app. Changes to the library's JavaScript code will be reflected in the example app without a rebuild, but native code changes will require a rebuild of the example app.
27
27
28
-
If you want to use Android Studio or Xcode to edit the native code, you can open the `apps/example/android` or `apps/example/ios` directories respectively in those editors. To edit the Objective-C or Swift files, open `apps/example/ios/ReleaseInspectorExample.xcworkspace` in Xcode and find the source files at `Pods > Development Pods > react-native-release-inspector`.
28
+
If you want to use Android Studio or Xcode to edit the native code, you can open the `apps/example/android` or `apps/example/ios` directories respectively in those editors. To edit the Objective-C or Swift files, open `apps/example/ios/InspectorExample.xcworkspace` in Xcode and find the source files at `Pods > Development Pods > inspector`.
29
29
30
-
To edit the Java or Kotlin files, open `apps/example/android` in Android studio and find the source files at `react-native-release-inspector` under `Android`.
30
+
To edit the Java or Kotlin files, open `apps/example/android` in Android studio and find the source files at `inspector` under `Android`.
31
31
32
32
You can use various commands from the root directory to work with the project.
33
33
@@ -52,7 +52,7 @@ yarn example ios
52
52
To confirm that the app is running with the new architecture, you can check the Metro logs for a message like this:
53
53
54
54
```sh
55
-
Running "ReleaseInspectorExample" with {"fabric":true,"initialProps":{"concurrentRoot":true},"rootTag":1}
55
+
Running "InspectorExample" with {"fabric":true,"initialProps":{"concurrentRoot":true},"rootTag":1}
56
56
```
57
57
58
58
Note the `"fabric":true` and `"concurrentRoot":true` properties.
The React on Web allows the users to run [profilable](https://react.dev/reference/dev-tools/react-performance-tracks#using-profiling-builds) builds to get near to production experience. This is the sweetest spot to having more confident profiling. However, on React Native this wasn't possible until now.
18
18
19
19
This package fixes this gap following the same analogy from React on Web, by allowing React Native to load Profiling shim for Release builds. 🚀
@@ -158,9 +156,9 @@ Now build and run your app in release mode, you should see the react devtools co
158
156
159
157
### API
160
158
161
-
The `@callstack/react-native-release-inspector` requires the user to configure their `metro.config` as shown above. This `withReactNativeReleaseInspector` receives the following arguments:
159
+
The `@callstack/inspector` requires the user to configure their `metro.config` as shown above. This `withInspector` receives the following arguments:
- User only need to pass the config instance from Metro
166
164
-`enabled: Boolean`
@@ -169,7 +167,7 @@ The `@callstack/react-native-release-inspector` requires the user to configure t
169
167
170
168
### CLI
171
169
172
-
The `@callstack/react-native-release-inspector` exposes a CLI `inspector` to start the instance of React DevTools.
170
+
The `@callstack/inspector` exposes a CLI `inspector` to start the instance of React DevTools.
173
171
174
172
It supports the following options:
175
173
@@ -181,9 +179,9 @@ It supports the following options:
181
179
Sample Usages:
182
180
183
181
```bash
184
-
yarn inspector start
185
-
yarn inspector help
186
-
yarn inspector -h
182
+
npx inspector start
183
+
npx inspector help
184
+
npx inspector -h
187
185
```
188
186
<hr/>
189
187
@@ -195,7 +193,7 @@ yarn inspector -h
195
193
196
194
## Made with ❤️ at Callstack
197
195
198
-
**react-native-release-inspector** is an open source project and will always remain free to use. If you think it's cool, please star it 🌟.
196
+
**inspector** is an open source project and will always remain free to use. If you think it's cool, please star it 🌟.
199
197
200
198
[Callstack](https://www.callstack.com/) is a group of React and React Native geeks, contact us at [hello@callstack.com](mailto:hello@callstack.com) if you need any help with these or just want to say hi!
201
199
@@ -207,9 +205,9 @@ Made with [create-react-native-library](https://github.com/callstack/react-nativ
0 commit comments