{
  "compilerOptions": {
    "target": "es2018",
    "lib": ["es2018"],
    "jsx": "react-native",
    "moduleResolution": "node",
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "rootDir": "./src",
    "outDir": "./build",
    "sourceMap": true,
    "inlineSources": true,
    "strictNullChecks": true,
    "strictPropertyInitialization": true,
    "strictFunctionTypes": true,
    "skipLibCheck": true,
    "noImplicitThis": true,
    "noImplicitReturns": true
  }
}

{
  "compilerOptions": {
    "target": "es2018",
    "lib": ["es2018"],
    "jsx": "react-native",
    "moduleResolution": "node",
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "types": ["jest"],
    "rootDir": "./src",
    "outDir": "./build",
    "sourceMap": true,
    "inlineSources": true,
    "strictNullChecks": true,
    "strictPropertyInitialization": true,
    "strictFunctionTypes": true,
    "skipLibCheck": true,
    "noImplicitThis": true,
    "noImplicitReturns": true
  }
}

Disable automatic inclusion of types, except for "jest"
[expo][ts] Disable automatic inclusion of types, except for "jest"

TypeScript's automatic inclusion finds global type definitions under `node_module/@types` and applies them. This is problematic for non-Node projects since the Node.js types are all global (for things like setTimeout, which was causing an issue for us), so if any dependency pulls in the Node types, we'd load them by default.

Setting `types: []` in the config disables only automatic inclusion. The TS docs say:

> Keep in mind that automatic inclusion is only important if you’re using files with global declarations (as opposed to files declared as modules). If you use an import "foo" statement, for instance, TypeScript may still look through `node_modules` & `node_modules/@types` folders to find the foo package.

We need to add back Jest so that test files know about Jest's globals. (Alternatively we could exclude tests from the regular tsconfig and include them only with the Jest tsconfig.)

Test plan: `yarn test` in the expo package when the expo repo is within Universe
