@schafevormfenster/eslint-config 0.0.19 → 0.0.21

package/.turbo/turbo-check.log

@@ -1,6 +1,6 @@
 
 
-> @schafevormfenster/eslint-config@0.0.18 check /Users/jan-henrik.hempel/Projects/commons/packages/eslint-config
+> @schafevormfenster/eslint-config@0.0.19 check /Users/jan-henrik.hempel/Projects/commons/packages/eslint-config
 > echo 'eslint-config: no build required'
 
 eslint-config: no build required

package/docs/RULES_REFERENCE.md

@@ -163,7 +163,9 @@ These configurations apply only to test files and should be added **after** your
 **Key rules**:
 - Enforce `*.test.ts`, `*.component.test.ts`, and `*.integration.test.ts` file naming
 - Prefer loose error matching (regex over exact strings)
-- Require environment setup hooks for env-var-based tests
+- Require environment setup hooks for env-var-based unit tests (`beforeEach`/`afterEach`)
+- Require environment guard hooks for integration tests (`beforeAll` throws if env var missing)
+- Forbid `delete process.env.*` in `beforeEach` in integration tests
 - No environment variable preservation
 - Forbid `vi.mock()`, `vi.spyOn()`, `vi.fn()` in integration tests
 - Forbid `it.skip()`, `it.skipIf()`, `describe.skip()`, `it.todo()`, etc. in integration tests
@@ -205,7 +207,8 @@ These configurations apply only to test files and should be added **after** your
 - Forbid `it.skip()`, `it.skipIf()`, `describe.skip()`, `it.todo()`, etc. — integration tests must always run
 - Prefer loose error matching (regex over exact strings)
 - No environment variable preservation
-- Require environment setup in beforeEach
+- Forbid `delete process.env.*` in `beforeEach` — env vars come from `.env` files, not test setup
+- Require a `beforeAll` guard that checks required env vars are present (env vars come from `.env` files / dotenv — integration tests must not set or delete them)
 - Require describe() wrappers for test organization
 - Enforce meaningful test descriptions
 - Suggest test categorization (Happy Path → Error → Edge Cases)
@@ -327,7 +330,9 @@ These rules apply across all Vitest tiers. Tier-specific rules (unit, component,
 | `prefer-loose-error-matching` | warn | all tiers | Prefer regex over exact string matching for errors |
 | `enforce-test-file-naming` | error | all tiers | Enforce `*.test.ts`, `*.component.test.ts`, `*.integration.test.ts` for Vitest tests |
 | `no-env-preservation-in-tests` | error | all tiers | Forbid preserving/restoring process.env (individual vars or entire env with `{ ...process.env }`) |
-| `require-env-setup-in-tests` | warn | unit, integration | Require beforeEach/afterEach in current describe or parent to handle env vars |
+| `require-env-setup-in-tests` | warn | unit | Require beforeEach/afterEach in current describe or parent to initialize/delete env vars |
+| `require-env-guard-in-integration-tests` | warn | integration | Require a `beforeAll` guard that checks required env vars are set before the suite runs (env vars come from `.env` files) |
+| `no-env-delete-in-before-each` | error | integration | Forbid `delete process.env.*` inside `beforeEach` — integration tests use env vars from `.env` files |
 | `no-mocks-in-integration-tests` | error | integration | Forbid `vi.mock()`, `vi.spyOn()`, and `vi.fn()` in integration tests |
 | `no-skip-in-integration-tests` | error | integration | Forbid `it.skip()`, `it.skipIf()`, `describe.skip()`, `it.todo()`, etc. — integration tests must always run |
 | `no-env-vars-in-component-tests` | error | component | Forbid `process.env` access in component tests |
@@ -361,7 +366,8 @@ These rules apply across all Vitest tiers. Tier-specific rules (unit, component,
 | `no-mocks-in-integration-tests` | error | Forbid `vi.mock()`, `vi.spyOn()`, and `vi.fn()` in integration tests |
 | `no-skip-in-integration-tests` | error | Forbid `it.skip()`, `it.skipIf()`, `describe.skip()`, `it.todo()`, etc. — integration tests must always run |
 | `no-env-preservation-in-tests` | error | Forbid preserving/restoring process.env (individual vars or entire env with `{ ...process.env }`) |
-| `require-env-setup-in-tests` | warn | Require beforeEach/afterEach in current describe or parent to handle env vars |
+| `no-env-delete-in-before-each` | error | Forbid `delete process.env.*` inside `beforeEach` — env vars come from `.env` files, not test setup |
+| `require-env-guard-in-integration-tests` | warn | Require a `beforeAll` guard that checks required env vars are set before the suite runs (env vars come from `.env` files) |
 | `require-describe-wrapper` | warn | Require test cases to be wrapped in describe() blocks |
 | `require-meaningful-descriptions` | warn | Require meaningful descriptions (min 10 chars for describe, 15 for it/test) |
 | `suggest-test-categorization` | warn | Suggest organizing tests into categories (Happy Path → Error → Edge Cases) |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@schafevormfenster/eslint-config",
-  "version": "0.0.19",
+  "version": "0.0.21",
   "publishConfig": {
     "access": "public"
   },
@@ -39,7 +39,7 @@
     "eslint-plugin-zod": "^1.4.0",
     "globals": "^16.5.0",
     "typescript-eslint": "^8.56.0",
-    "@schafevormfenster/eslint-plugin": "0.0.19"
+    "@schafevormfenster/eslint-plugin": "0.0.21"
   },
   "engines": {
     "node": ">=22"