Skip to content

secondsky/claude-skills / plugins/dependency-upgrade/skills/dependency-upgrade

dependency-upgrade

Unverified

Secure dependency upgrades with supply chain protection, cooldowns, and staged rollout. Use when upgrading deps, configuring security policies, or preventing supply chain attacks.

references/compatibility-matrix.md

View on GitHub
# Dependency Compatibility Matrix

Common version compatibility requirements for major frameworks and libraries.

## React Ecosystem

| React | react-dom | react-router | @testing-library/react | Next.js |
|-------|-----------|--------------|----------------------|---------|
| 18.x  | ^18.0.0   | ^6.0.0       | ^14.0.0              | 13.x-14.x |
| 19.x  | ^19.0.0   | ^7.0.0       | ^16.0.0              | 15.x |

### React 18 → 19 Migration

```bash
bun add react@19 react-dom@19
bun add -D @testing-library/react@16 @types/react@19 @types/react-dom@19
```

Key breaking changes:
- Ref as prop (no more `forwardRef` needed)
- `useDeferredValue` initial value support
- Improved hydration mismatch reporting
- `ref` cleanup functions return value is ignored

### React Router 6 → 7

```bash
bun add react-router@7 react-router-dom@7
```

React Router v7 is the successor to Remix and React Router v6. Key changes:
- Framework mode (Remix-like) vs library mode
- New `createRootRoute`, `createRouter` API
- Data loading via `loader` and `action`

## Next.js

| Next.js | React | Node.js | TypeScript |
|---------|-------|---------|------------|
| 13.x    | 18.x  | >=16.8  | >=4.5      |
| 14.x    | 18.x  | >=18.17 | >=4.5      |
| 15.x    | 18.x-19.x | >=20.9  | >=4.5  |

> **Node.js EOL note:** Node 16 reached EOL 2023-09 and Node 18 reached EOL 2025-04. The `>=16.8`/`>=18.17` floors above reflect each Next.js major's *minimum* at release; for *current* projects use Node 20+ (the row above for Next 15 already mandates `>=20.9`). Do not start new work on Node 16 or 18.

### Next.js 14 → 15 Migration

```bash
bun add next@15
```

Key breaking changes:
- Turbopack as default dev bundler
- Improved caching defaults (fetch requests no longer cached by default)
- `next/image` changes
- Node.js >=20.9 required

## TypeScript

| TypeScript | Node.js target | Key feature |
|-----------|---------------|-------------|
| 5.3       | ES2022+       | `using` keyword, `Symbol.dispose` |
| 5.4       | ES2022+       | NoInfer utility type |
| 5.5       | ES2022+       | Inferred type predicates |
| 5.6       | ES2022+       | Iterator helpers |
| 5.7       | ES2024+       | `--target es2024`, path renaming |

### TypeScript Upgrade

```bash
bun add -D typescript@latest
```

TypeScript upgrades are typically backward compatible. Run type-check after upgrade:

```bash
bunx tsc --noEmit
```

## Tailwind CSS

| Tailwind | PostCSS | Framework support |
|----------|---------|-------------------|
| 3.x      | >=8.4   | All frameworks |
| 4.x      | Built-in | All frameworks (new engine) |

### Tailwind 3 → 4 Migration

```bash
bun add -D tailwindcss@4 @tailwindcss/vite
```

Key changes:
- CSS-first configuration (`@theme` instead of `tailwind.config.js`)
- Required primary entrypoint: `@import "tailwindcss"`
- PostCSS plugin via `@tailwindcss/postcss` package (must install and configure)
- Lightning CSS can replace PostCSS in some setups per official Tailwind recommendations
- New `@source inline("class-name")` pattern for safelisting utilities

## Node.js Version Compatibility

| Node.js | npm version | npm ci support |
|---------|------------|----------------|
| 18 LTS | 9.x        | Yes            |
| 20 LTS | 10.x       | Yes            |
| 22 LTS | 10.x       | Yes            |

See [Node.js Release Schedule](https://nodejs.org/en/about/releases) for LTS dates.

## Checking Compatibility

```bash
# Check peer dependency warnings
npm ls 2>&1 | grep -i "peer dep"

# Check for outdated with compatibility info
npm outdated

# Use npm-check-updates for safe upgrade analysis
bunx npm-check-updates --interactive

# Check for known vulnerabilities
npm audit
bun audit
```
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall