Gathering detailed insights and metrics for @xhsfe/react-native-community-cli-plugin-metro
Gathering detailed insights and metrics for @xhsfe/react-native-community-cli-plugin-metro
Gathering detailed insights and metrics for @xhsfe/react-native-community-cli-plugin-metro
Gathering detailed insights and metrics for @xhsfe/react-native-community-cli-plugin-metro
The React Native Community CLI - command line tools to help you build RN apps
npm install @xhsfe/react-native-community-cli-plugin-metro
Typescript
Module System
Node Version
NPM Version
TypeScript (95.73%)
JavaScript (1.97%)
HTML (1.08%)
Java (0.57%)
Kotlin (0.42%)
Shell (0.09%)
Objective-C (0.08%)
Ruby (0.05%)
Batchfile (0.02%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
2,667 Stars
2,660 Commits
926 Forks
47 Watchers
53 Branches
551 Contributors
Updated on Jul 12, 2025
Latest Version
11.4.1-red.0
Package Id
@xhsfe/react-native-community-cli-plugin-metro@11.4.1-red.0
Unpacked Size
64.95 kB
Size
15.46 kB
File Count
42
NPM Version
10.8.2
Node Version
18.20.5
Published on
Jan 09, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
This package is part of the React Native CLI. It contains commands for managing the Metro bundler.
1yarn add @react-native-community/cli-plugin-metro
start
Usage:
1react-native start [option]
Starts the server that communicates with connected devices
--port <number>
Specify port to listen on
--projectRoot <path>
Path to a custom project root
--watchFolders <list>
Specify any additional folders to be added to the watch list
--assetPlugins <list>
Specify any additional asset plugins to be used by the packager by full filepath
--sourceExts <list>
Specify any additional source extensions to be used by the packager
--max-workers <number>
Specifies the maximum number of workers the worker-pool will spawn for transforming files. This defaults to the number of the cores available on your machine
--transformer <string>
Specify a custom transformer to be used
--reset-cache, --resetCache
Removes cached files
--custom-log-reporter-path, --customLogReporterPath <string>
Path to a JavaScript file that exports a log reporter as a replacement for TerminalReporter
--https
Enables https connections to the server
--key <path>
Path to custom SSL key
--cert <path>
Path to custom SSL cert
--config <string>
Path to the CLI configuration file
--no-interactive
Disables interactive mode
bundle
Usage:
1react-native bundle <flag>
Builds the JavaScript bundle for offline use.
--entry-file <path>
Path to the root JS file, either absolute or relative to JS root.
--platform <string>
default: ios
Either "ios" or "android".
--transformer <string>
Specify a custom transformer to be used.
--dev [boolean]
default: true
If false, warnings are disabled and the bundle is minified.
--minify [boolean]
Allows overriding whether bundle is minified. This defaults to false if dev is true, and true if dev is false. Disabling minification can be useful for speeding up production builds for testing purposes.
--bundle-output <string>
File name where to store the resulting bundle, ex. /tmp/groups.bundle
.
If you are planning on building a debug APK, that will run without the packager, by invoking ./gradlew assembleDebug
you can simply set bundleInDebug: true
in your app/build.gradle file, inside the project.ext.react
map.
react-native bundle
manually and then create the APK with ./gradlew assembleDebug
you have to make sure to put the bundle into the right directory and give it the right name, so that gradle can find it.
For react-native versions 0.57 and above the bundle output path should be:
android/app/build/generated/assets/react/debug/index.android.js
To find out the correct path for previous react-native versions, take a look at the react.gradle
file here: https://github.com/facebook/react-native/blob/0.57-stable/react.gradle or inside your node_modules/react-native
directory.
The expected path for the js bundle can be found on the line that starts with jsBundleDir =
.
--bundle-encoding <string>
default: utf8
Encoding the bundle should be written in (https://nodejs.org/api/buffer.html#buffer_buffer).
--max-workers <number>
Specifies the maximum number of workers the worker-pool will spawn for transforming files. This defaults to the number of the cores available on your machine.
--sourcemap-output <string>
File name where to store the sourcemap file for resulting bundle, ex. /tmp/groups.map
.
--sourcemap-sources-root <string>
Path to make sourcemap sources entries relative to, ex. /root/dir
.
--sourcemap-use-absolute-path
default: false
Report SourceMapURL using its full path.
--assets-dest <string>
Directory name where to store assets referenced in the bundle.
If you are planning on building a debug APK that will run without the packager, see (--bundle-output)
react-native bundle
manually and then create the APK with ./gradlew assembleDebug
you have to make sure to put the assets into the right directory, so that gradle can find them.
For react-native versions 0.57 and above the --assets-dest
path should be:
android/app/build/generated/res/react/debug
The expected path for the assets can be found in the react.gradle file on the line that starts with resourcesDir =
--reset-cache
default: false
Removes cached files.
--read-global-cache
default: false
Try to fetch transformed JS code from the global cache, if configured.
--config <string>
Path to the CLI configuration file.
ram-bundle
Usage:
1react-native ram-bundle [options]
Builds JavaScript as a "Random Access Module" bundle for offline use.
Accepts all of bundle commands and following:
--indexed-ram-bundle
Force the "Indexed RAM" bundle file format, even when building for Android.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
13 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
Found 21/30 approved changesets -- score normalized to 7
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Reason
15 existing vulnerabilities detected
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More