@infinitetoken/eslint-config 0.1.7 → 0.2.0

package/README.md

@@ -9,6 +9,7 @@ Shared ESLint (flat config) and Prettier rules for InfiniteToken TypeScript pack
 | `@infinitetoken/eslint-config` | Universal core (TS recommended, prettier, import sort); rarely used directly. Always ignores `dist/**`, `node_modules/**`, `lib/**`, `coverage/**`, `**/*.js`, `**/*.mjs`, `.claude/worktrees/**` (a Claude Code artifact directory present across the whole fleet), and `.yalc/**` (yalc-linked packages snapshot their `.d.ts`/`.d.mts` output too, not just compiled JS — those crash the type-aware parser the same as any other out-of-project `.ts` file if not ignored) |
 | `@infinitetoken/eslint-config/npm-package` | Any published npm package with no React Native or server specifics (kits, Node plugins). Also ignores `tsup.config.ts` (a no-op if the package doesn't have one — it sits outside the rootDir-scoped tsconfig most kit packages use, which trips the type-aware parser if linted) and turns off `no-explicit-any` under `**/__tests__/**` and `**/__mocks__/**` — those directories are linted like anywhere else (formatting, import sort, unused vars), not excluded; `any` is just a reasonable choice there for casting fixtures and mocking modules |
 | `@infinitetoken/eslint-config/react-native` | React Native packages; adds `eslint-plugin-react-hooks` and `eslint-plugin-react-native` |
+| `@infinitetoken/eslint-config/expo` | Expo apps (not libraries); layers `eslint-config-expo/flat` underneath `/react-native`, so the fleet's conventions (the `^_` unused-vars pattern, import sort, `package.json` rules, etc.) win over Expo's own defaults. Also ignores `ios/**`, `android/**`, `.expo/**`, `.vscode/**` |
 | `@infinitetoken/eslint-config/server` | Express/server apps; relaxed `no-unused-vars` (`^_` ignore pattern), `no-explicit-any: warn`, skips the `package.json` plugin since these aren't published |
 | `@infinitetoken/eslint-config/vue` | Vue/Nuxt apps; adds `vue-eslint-parser` + `eslint-plugin-vue`'s `flat/recommended`, no type-aware TS parsing (Nuxt's generated tsconfig makes that awkward) |
 | `@infinitetoken/eslint-config/prettier` | The shared Prettier rules object, for the `"prettier"` field in `package.json` |
@@ -40,7 +41,7 @@ module.exports = defineConfig([
 
 `eslint` itself is a peer dependency (`^9.9.0 || ^10.0.0`); keep it as your own devDependency for the CLI binary. Most plugins the config requires (`typescript-eslint`, `eslint-plugin-prettier`, `eslint-plugin-simple-import-sort`, `eslint-plugin-package-json`, `eslint-plugin-vue`, `vue-eslint-parser`, `prettier`) ship as regular dependencies of this package, so consumers don't list or version them individually.
 
-`eslint-plugin-react-hooks` and `eslint-plugin-react-native` are the exception: they're optional peer dependencies instead, only needed by the `/react-native` preset. `eslint-plugin-react-native@5` currently only supports `eslint` up to v9, so bundling it as a regular dependency would force that ceiling onto every consumer, not just React Native ones. If you use the `/react-native` preset, add both as your own devDependencies (matching what the RN packages already do today).
+`eslint-plugin-react-hooks`, `eslint-plugin-react-native`, and `eslint-config-expo` are the exception: they're optional peer dependencies instead, only needed by the `/react-native` and `/expo` presets. `eslint-plugin-react-native@5` currently only supports `eslint` up to v9, so bundling it as a regular dependency would force that ceiling onto every consumer, not just React Native ones. `eslint-config-expo` is versioned to track a specific Expo SDK release (this package pins `^57.0.0`, matching Expo SDK 57), so bundling it would tie every consumer — including non-Expo ones — to one SDK's requirements. If you use the `/react-native` preset, add `eslint-plugin-react-hooks` and `eslint-plugin-react-native` as your own devDependencies; if you use `/expo`, add those two plus `eslint-config-expo` (matching what the RN/Expo apps already do today).
 
 ## Release
 

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@infinitetoken/eslint-config",
-  "version": "0.1.7",
+  "version": "0.2.0",
   "description": "Shared ESLint and Prettier configuration for InfiniteToken TypeScript packages",
   "keywords": [
     "config",
@@ -22,6 +22,7 @@
   "type": "commonjs",
   "exports": {
     ".": "./src/index.cjs",
+    "./expo": "./src/expo.cjs",
     "./npm-package": "./src/npm-package.cjs",
     "./prettier": "./src/prettier.cjs",
     "./react-native": "./src/react-native.cjs",
@@ -57,15 +58,20 @@
   },
   "devDependencies": {
     "eslint": "^9.39.4",
+    "eslint-config-expo": "^57.0.2",
     "eslint-plugin-react-hooks": "^7.1.1",
     "eslint-plugin-react-native": "^5.0.0"
   },
   "peerDependencies": {
     "eslint": "^9.9.0 || ^10.0.0",
+    "eslint-config-expo": "^57.0.0",
     "eslint-plugin-react-hooks": "^7.0.0",
     "eslint-plugin-react-native": "^5.0.0"
   },
   "peerDependenciesMeta": {
+    "eslint-config-expo": {
+      "optional": true
+    },
     "eslint-plugin-react-hooks": {
       "optional": true
     },

package/src/expo.cjs

@@ -0,0 +1,11 @@
+const { defineConfig } = require('eslint/config')
+const expoConfig = require('eslint-config-expo/flat')
+const reactNative = require('./react-native.cjs')
+
+module.exports = defineConfig([
+  {
+    ignores: ['ios/**', 'android/**', '.expo/**', '.vscode/**']
+  },
+  ...expoConfig,
+  ...reactNative
+])

package/src/index.cjs

@@ -28,7 +28,13 @@ module.exports = defineConfig([
       'simple-import-sort/imports': 'warn',
       'simple-import-sort/exports': 'warn',
       'no-console': 'warn',
-      '@typescript-eslint/no-unused-vars': 'warn',
+      // '_'-prefixed unused var/arg/caught-error bindings are a deliberate "I need this position,
+      // not this value" signal (most commonly an object-destructure used only to omit a key, e.g.
+      // `const { id: _id, ...rest } = obj` — unlike array destructuring, an object key binding can't
+      // be elided) and shouldn't warn. Universal fleet-wide: a grep across every repo in the fleet
+      // found zero consumers of this bare `.` export, so there's no real "wants the plain warn
+      // instead" consumer to preserve by scoping this to individual presets instead.
+      '@typescript-eslint/no-unused-vars': ['warn', { varsIgnorePattern: '^_', argsIgnorePattern: '^_', caughtErrorsIgnorePattern: '^_' }],
       '@typescript-eslint/no-require-imports': 'off'
     }
   }

package/src/react-native.cjs

@@ -14,6 +14,7 @@ module.exports = defineConfig([
       'react-native/no-inline-styles': 'warn',
       'react-native/no-unused-styles': 'warn',
       'react-native/no-raw-text': 'off',
+      'react-native/sort-styles': 'warn',
       // rules-of-hooks stays at error since it's the foundational hook-ordering check, not a
       // judgment call. The rest match the fleet's severities (warn, not error).
       'react-hooks/rules-of-hooks': 'error',

package/src/server.cjs

@@ -5,7 +5,6 @@ module.exports = defineConfig([
   ...base,
   {
     rules: {
-      '@typescript-eslint/no-unused-vars': ['warn', { varsIgnorePattern: '^_', argsIgnorePattern: '^_', caughtErrorsIgnorePattern: '^_' }],
       '@typescript-eslint/no-explicit-any': 'warn'
     }
   },