When using react-native start, its platform derivatives, and react-native bundle you can use a file to define the CLI options used by React Native by default. If you create a file rn-cli.config.js in the root of your project, it will be evaluated and options for the commands will come from there.
You can see the options for the CLI config file inside the source code for Metro here, and here is a common rn-cli.config.js used for supporting TypeScript in React Native projects:
You can see the options for the CLI config file inside the source code for Metro here, and here is a common rn-cli.config.js used for supporting TypeScript in React Native projects:
module.exports = {
getTransformModulePath() {
return require.resolve('react-native-typescript-transformer');
diff --git a/docs/next/understanding-cli/index.html b/docs/next/understanding-cli/index.html
index dcd73376a08..48e09097c53 100644
--- a/docs/next/understanding-cli/index.html
+++ b/docs/next/understanding-cli/index.html
@@ -76,7 +76,7 @@
When using react-native start, its platform derivatives, and react-native bundle you can use a file to define the CLI options used by React Native by default. If you create a file rn-cli.config.js in the root of your project, it will be evaluated and options for the commands will come from there.
You can see the options for the CLI config file inside the source code for Metro here, and here is a common rn-cli.config.js used for supporting TypeScript in React Native projects:
You can see the options for the CLI config file inside the source code for Metro here, and here is a common rn-cli.config.js used for supporting TypeScript in React Native projects:
module.exports = {
getTransformModulePath() {
return require.resolve('react-native-typescript-transformer');