This package is part of the React Native CLI. It contains commands for managing the Metro bundler.
yarn add @react-native-community/cli-plugin-metro
Usage:
npx react-native start [option]
Starts the server that communicates with connected devices
Specify port to listen on
Path to a custom project root
Specify any additional folders to be added to the watch list
Specify any additional asset plugins to be used by the packager by full filepath
Specify any additional source extensions to be used by the packager
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
Specify a custom transformer to be used
Removes cached files
Path to a JavaScript file that exports a log reporter as a replacement for TerminalReporter
Enables https connections to the server
Path to custom SSL key
Path to custom SSL cert
Path to the CLI configuration file
Disables interactive mode
Usage:
npx react-native bundle <flag>
Builds the JavaScript bundle for offline use.
Path to the root JS file, either absolute or relative to JS root.
default: ios
Either "ios" or "android".
Specify a custom transformer to be used.
default: true
If false, warnings are disabled and the bundle is minified.
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.
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.
npx 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 =
.
default: utf8
Encoding the bundle should be written in (https://nodejs.org/api/buffer.html#buffer_buffer).
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.
File name where to store the sourcemap file for resulting bundle, ex. /tmp/groups.map
.
Path to make sourcemap sources entries relative to, ex. /root/dir
.
default: false
Report SourceMapURL using its full path.
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)
npx 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 =
default: false
Removes cached files.
default: false
Try to fetch transformed JS code from the global cache, if configured.
Path to the CLI configuration file.
Usage:
npx react-native ram-bundle [options]
Builds JavaScript as a "Random Access Module" bundle for offline use.
Accepts all of bundle commands and following:
Force the "Indexed RAM" bundle file format, even when building for Android.