ts-qa-ci/package.json at main · LongTermSupport/ts-qa-ci · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
{
  "name": "@longtermsupport/ts-qa-ci",
  "version": "0.1.0",
  "description": "Orchestrated QA/CI pipeline for TypeScript/React projects - the TS analogue of lts/php-qa-ci",
  "license": "MIT",
  "type": "module",
  "bin": {
    "ts-qa": "bin/ts-qa.js"
  },
  "main": "dist/index.js",
  "types": "dist/index.d.ts",
  "exports": {
    ".": {
      "types": "./dist/index.d.ts",
      "default": "./dist/index.js"
    }
  },
  "files": [
    "dist",
    "bin",
    "configDefaults",
    "docs",
    "skills",
    "agents"
  ],
  "scripts": {
    "build": "tsc -p tsconfig.json",
    "test": "vitest run",
    "prepublishOnly": "npm run build"
  },
  "_peerDependenciesPolicy": "Floors are set to the CURRENT major generation as of the last version check (npm view <pkg> version), not an old baseline carried forward out of habit — ts-qa-ci should push consumers toward current stable tooling, not accommodate years-old installs. Re-run `npm view <pkg> version` for every peerDependency before each ts-qa-ci release and bump these floors to the then-current major; do not silently let them go stale. EXCEPTIONS (both found 2026-07-10 while dogfooding on lts-commerce-site, Plan 011 Task 4.1 — verify `npm view <plugin> peerDependencies` for the key ecosystem plugin, not just the tool's own version, before raising either floor again): (1) typescript is capped below its own latest major because typescript-eslint 8.63.0 (latest, and its canary) still caps at `typescript >=4.8.4 <6.1.0` even though TypeScript 7.x has shipped stable — floor set to 6.0.3, the newest version actually inside that ceiling. (2) eslint is capped below its own latest major because eslint-plugin-react 7.37.5 (latest, last published 2025-04-03, no `next` tag support for it either) still caps at `eslint ^3...^9.7` — using ESLint 10 would break every consumer running eslint-plugin-react (i.e. effectively every React consumer). Floor set to 9.39.4, the newest 9.x release.",
  "peerDependencies": {
    "@playwright/test": ">=1.60.0",
    "@stryker-mutator/core": ">=9.0.0",
    "@types/node": ">=22.0.0",
    "eslint": ">=9.7.0",
    "prettier": ">=3.9.0",
    "typescript": ">=6.0.0",
    "typescript-eslint": ">=8.0.0",
    "vite": ">=8.0.0",
    "vitest": ">=4.0.0"
  },
  "peerDependenciesMeta": {
    "typescript-eslint": {
      "optional": true
    },
    "vite": {
      "optional": true
    },
    "vitest": {
      "optional": true
    },
    "@playwright/test": {
      "optional": true
    },
    "@stryker-mutator/core": {
      "optional": true
    }
  },
  "dependencies": {
    "dependency-cruiser": "^18.0.0",
    "eslint-config-prettier": "^10.0.0",
    "knip": "^6.0.0",
    "oxlint": "^1.72.0",
    "remark": "^15.0.0",
    "remark-validate-links": "^13.0.0",
    "vfile": "^6.0.0"
  },
  "devDependencies": {
    "@types/estree": "^1.0.0",
    "@types/estree-jsx": "^1.0.0",
    "@types/node": "^22.0.0",
    "@typescript-eslint/parser": "^8.63.0",
    "eslint": "^9.39.4",
    "typescript": "^6.0.3",
    "typescript-eslint": "^8.63.0",
    "vitest": "^4.0.0"
  },
  "engines": {
    "node": ">=22.0.0"
  }
}