@rm30/tsconfig 0.1.0

package/README.md

@@ -0,0 +1,93 @@
+# @rm30/tsconfig
+
+Shared TypeScript configurations. Four, matching the four shapes of code in the workspace.
+
+```sh
+pnpm add -D @rm30/tsconfig
+```
+
+**Declare it in every package that extends it**, not only at the monorepo root. Root-only
+works today because both Expo monorepos set `nodeLinker: hoisted`, which flattens
+`node_modules` so a nested package resolves upward into it. A project on pnpm's default
+strict linker would not, and a package should declare what it uses regardless.
+
+| Config | For |
+|---|---|
+| `@rm30/tsconfig/base.json` | Everything else builds on this. Strictness and interop only — no emit decisions, no JSX. |
+| `@rm30/tsconfig/next.json` | A Next.js app. |
+| `@rm30/tsconfig/expo.json` | An Expo app — see the note below, it is used differently. |
+| `@rm30/tsconfig/node-lib.json` | A Node package that emits declarations (Firebase functions, a published lib). |
+
+## `include`, `exclude` and `paths` stay in the project
+
+None of these configs set `include` or `exclude`, and that is not an oversight.
+TypeScript resolves relative paths **against the config file they are written in**, so an
+`include: ["src"]` shipped from here would resolve inside
+`node_modules/@rm30/tsconfig/` and match nothing. The same goes for `paths`, which points
+at the project's own directories anyway.
+
+So every project declares its own file set:
+
+```json
+{
+  "extends": "@rm30/tsconfig/next.json",
+  "compilerOptions": {
+    "paths": { "@/*": ["./src/*"] }
+  },
+  "include": ["next-env.d.ts", "**/*.ts", "**/*.tsx", ".next/types/**/*.ts"],
+  "exclude": ["node_modules"]
+}
+```
+
+## Expo app
+
+Expo ships its own base, and it is not optional — it carries the React Native type
+resolution. So an Expo app extends **both**, ours last:
+
+```json
+{
+  "extends": ["expo/tsconfig.base", "@rm30/tsconfig/expo.json"],
+  "compilerOptions": {
+    "paths": { "@/*": ["./src/*"] }
+  }
+}
+```
+
+Array `extends` needs TypeScript 5.0+; later entries win.
+
+`expo.json` deliberately does **not** extend `base.json`. It would have to reach
+`expo/tsconfig.base` from inside `node_modules/@rm30/tsconfig/`, where pnpm's symlinked
+store gives it no view of the consuming project's `expo` — so the extend would resolve in
+development and break for anyone else. Composing the two in the project keeps resolution
+where the packages actually are.
+
+## Node library
+
+```json
+{
+  "extends": "@rm30/tsconfig/node-lib.json",
+  "compilerOptions": {
+    "outDir": "lib",
+    "rootDir": "src"
+  }
+}
+```
+
+`outDir` and `rootDir` stay local — they are layout, not policy.
+
+Note that most internal packages should **not** use this. A package consumed only inside
+its own monorepo should be source-direct: `main` and `types` pointing at `src/index.ts`,
+no build step at all. Metro, Next and tsup all read TypeScript from source, so compiling
+buys nothing and costs a build that CI must run before anything type-checks. `node-lib` is
+for the cases that genuinely emit — Firebase functions, or a package published to npm.
+
+## What base sets
+
+`target`/`lib` ES2022, `module` ESNext, `moduleResolution` bundler, `strict`,
+`isolatedModules`, `esModuleInterop`, `allowSyntheticDefaultImports`, `resolveJsonModule`,
+`forceConsistentCasingInFileNames`, `skipLibCheck`.
+
+`moduleResolution: bundler` is deliberate. The old `node` (node10) mode is deprecated as
+of TypeScript 6 and errors without an `ignoreDeprecations` escape hatch, and every RM30
+package is either bundled or consumed by a bundler, so `bundler` is simply the accurate
+description.

package/base.json

@@ -0,0 +1,20 @@
+{
+  "$schema": "https://json.schemastore.org/tsconfig",
+  "display": "RM30 base",
+  "compilerOptions": {
+    "target": "ES2022",
+    "lib": [
+      "ES2022"
+    ],
+    "module": "ESNext",
+    "moduleResolution": "bundler",
+    "strict": true,
+    "forceConsistentCasingInFileNames": true,
+    "isolatedModules": true,
+    "esModuleInterop": true,
+    "allowSyntheticDefaultImports": true,
+    "resolveJsonModule": true,
+    "skipLibCheck": true,
+    "skipDefaultLibCheck": true
+  }
+}

package/expo.json

@@ -0,0 +1,12 @@
+{
+  "$schema": "https://json.schemastore.org/tsconfig",
+  "display": "RM30 Expo app",
+  "compilerOptions": {
+    "strict": true,
+    "forceConsistentCasingInFileNames": true,
+    "esModuleInterop": true,
+    "allowSyntheticDefaultImports": true,
+    "resolveJsonModule": true,
+    "skipLibCheck": true
+  }
+}

package/next.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://json.schemastore.org/tsconfig",
+  "display": "RM30 Next.js app",
+  "extends": "./base.json",
+  "compilerOptions": {
+    "target": "ES2017",
+    "lib": [
+      "dom",
+      "dom.iterable",
+      "esnext"
+    ],
+    "jsx": "preserve",
+    "allowJs": true,
+    "noEmit": true,
+    "incremental": true,
+    "plugins": [
+      {
+        "name": "next"
+      }
+    ]
+  }
+}

package/node-lib.json

@@ -0,0 +1,16 @@
+{
+  "$schema": "https://json.schemastore.org/tsconfig",
+  "display": "RM30 Node library (emits)",
+  "extends": "./base.json",
+  "compilerOptions": {
+    "module": "nodenext",
+    "moduleResolution": "nodenext",
+    "types": [
+      "node"
+    ],
+    "declaration": true,
+    "declarationMap": true,
+    "sourceMap": true,
+    "noImplicitReturns": true
+  }
+}

package/package.json

@@ -0,0 +1,23 @@
+{
+  "name": "@rm30/tsconfig",
+  "version": "0.1.0",
+  "description": "Shared RM30 TypeScript configurations — base, expo, next, node-lib.",
+  "license": "MIT",
+  "author": "Rafael Miziara",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/rafamiziara/cli.git",
+    "directory": "packages/tsconfig"
+  },
+  "keywords": ["tsconfig", "typescript"],
+  "exports": {
+    "./base.json": "./base.json",
+    "./expo.json": "./expo.json",
+    "./next.json": "./next.json",
+    "./node-lib.json": "./node-lib.json"
+  },
+  "files": ["base.json", "expo.json", "next.json", "node-lib.json", "README.md"],
+  "publishConfig": {
+    "access": "public"
+  }
+}