docs: add info about package.json entrypoint

Author: satya164

docs/pages/build.md

@@ -80,7 +80,6 @@ To configure your project manually, follow these steps:
    "source": "./src/index.tsx",
    "main": "./lib/commonjs/index.js",
    "module": "./lib/module/index.js",
-   "types": "./lib/typescript/commonjs/src/index.d.ts",
    "exports": {
      ".": {
        "import": {
@@ -91,7 +90,8 @@ To configure your project manually, follow these steps:
          "types": "./lib/typescript/commonjs/src/index.d.ts",
          "default": "./lib/commonjs/index.js"
        }
-     }
+     },
+     "./package.json": "./package.json"
    },
    "files": [
      "lib",
@@ -104,7 +104,6 @@ To configure your project manually, follow these steps:
    - `source`: The path to the source code. It is used by `react-native-builder-bob` to detect the correct output files and provide better error messages.
    - `main`: The entry point for the CommonJS build. This is used by Node - such as tests, SSR etc.
    - `module`: The entry point for the ES module build. This is used by bundlers such as webpack.
-   - `types`: The entry point for the TypeScript definitions. This is used by TypeScript to typecheck the code using your library.
    - `files`: The files to include in the package when publishing with `npm`.
    - `exports`: The entry points for tools that support the `exports` field in `package.json` - such as Node.js 12+ & modern browsers. See [the ESM support guide](./esm.md) for more details.
 

docs/pages/esm.md

@@ -36,7 +36,6 @@ To make use of the output files, ensure that your `package.json` file contains t
 ```json
 "main": "./lib/commonjs/index.js",
 "module": "./lib/module/index.js",
-"types": "./lib/typescript/commonjs/src/index.d.ts",
 "exports": {
   ".": {
     "import": {
@@ -47,23 +46,29 @@ To make use of the output files, ensure that your `package.json` file contains t
       "types": "./lib/typescript/commonjs/src/index.d.ts",
       "default": "./lib/commonjs/index.js"
     }
-  }
+  },
+  "./package.json": "./package.json"
 },
 ```
 
 The `main`, `module` and `types` fields are for legacy setups that don't support the `exports` field. See the [Manual configuration](build.md#manual-configuration) guide for more information about those fields.
 
-The `exports` field is used by modern tools and bundlers to determine the correct entry point. Here, we specify 2 conditions:
+The `exports` field is used by modern tools and bundlers to determine the correct entry point. The entrypoint is specified in the `.` key and will be used when the library is imported or required directly (e.g. `import 'my-library'` or `require('my-library')`).
+
+Here, we specify 2 conditions:
 
 - `import`: Used when the library is imported with an `import` statement or a dynamic `import()`. It should point to the ESM build.
 - `require`: Used when the library is required with a `require` call. It should point to the CommonJS build.
 
-Each condition has a `types` field - necessary for TypeScript to provide the appropriate definitions for the module system. The type definitions have slightly different semantics for CommonJS and ESM, so it's important to specify them separately.
+Each condition has 2 fields:
 
-The `default` field is the fallback entry point for both conditions. It's used for the actual JS code when the library is imported or required.
+- `types`: necessary for TypeScript to provide the appropriate definitions for the module system. The type definitions have slightly different semantics for CommonJS and ESM, so it's important to specify them separately.
+- `default`: fallback entry point for both conditions. It's used for the actual JS code when the library is imported or required.
 
 You can also specify additional conditions for different scenarios, such as `react-native`, `browser`, `production`, `development` etc. Note that support for these conditions depends on the tooling you're using.
 
+The `./package.json` field is used to point to the library's `package.json` file. It's necessary for tools that may need to read the `package.json` file directly (e.g. [React Native Codegen](https://reactnative.dev/docs/the-new-architecture/what-is-codegen)).
+
 ## Guidelines
 
 There are still a few things to keep in mind if you want your library to be ESM-compatible:
@@ -96,6 +101,7 @@ There are still a few things to keep in mind if you want your library to be ESM-
         "react-native": "./lib/commonjs/index.native.js",
         "default": "./lib/commonjs/index.js"
       }
-    }
+    },
+    "./package.json": "./package.json"
   }
   ```

docs/pages/faq.md

@@ -135,7 +135,8 @@ If you have a reason to not ship Codegen generated scaffold code with your libra
    ```diff
    "codegenConfig": {
      // …
-   +   "includesGeneratedCode": false
+   - "includesGeneratedCode": true
+   + "includesGeneratedCode": false
    }
    ```
 
@@ -146,16 +147,18 @@ If you have a reason to not ship Codegen generated scaffold code with your libra
     "output": "lib",
     "targets": [
       // …
-   -   "codegen"
+   -  "codegen"
     ]
    ```
 
 3. If you have an `exports` field in your `package.json`, ensure that it contains `./package.json`:
 
    ```diff
    "exports": {
-     // …
-   +   "./package.json": "./package.json"
+     ".": {
+       // …
+     },
+   + "./package.json": "./package.json"
    },
    ```