diff --git a/docs/next/typescript.html b/docs/next/typescript.html index 59c3bf6aa29..9db87673c23 100644 --- a/docs/next/typescript.html +++ b/docs/next/typescript.html @@ -122,8 +122,13 @@ npm install --save-dev typescript @types/jest @types/react @types/react-native @ };
Rename a JavaScript file to be *.tsx
Run yarn tsc to type-check your new TypeScript files.
*.tsx++You should leave the
+./index.jsentrypoint file as it is otherwise you may run into an issue when it comes to bundling a production build.
yarn tsc to type-check your new TypeScript files.Out of the box, transforming your files to JavaScript works via the same Babel infrastructure as a non-TypeScript React Native project. We recommend that you use the TypeScript compiler only for type checking. If you have existing TypeScript code being ported to React Native, there are one or two caveats to using Babel instead of TypeScript.
diff --git a/docs/next/typescript/index.html b/docs/next/typescript/index.html index 59c3bf6aa29..9db87673c23 100644 --- a/docs/next/typescript/index.html +++ b/docs/next/typescript/index.html @@ -122,8 +122,13 @@ npm install --save-dev typescript @types/jest @types/react @types/react-native @ };Rename a JavaScript file to be *.tsx
Run yarn tsc to type-check your new TypeScript files.
*.tsx++You should leave the
+./index.jsentrypoint file as it is otherwise you may run into an issue when it comes to bundling a production build.
yarn tsc to type-check your new TypeScript files.Out of the box, transforming your files to JavaScript works via the same Babel infrastructure as a non-TypeScript React Native project. We recommend that you use the TypeScript compiler only for type checking. If you have existing TypeScript code being ported to React Native, there are one or two caveats to using Babel instead of TypeScript.