json-server icon indicating copy to clipboard operation
json-server copied to clipboard

[WIP] Update all dev dependencies

Open Copilot opened this issue 4 months ago • 1 comments

Update all dev dependencies

Plan:

  • [x] Analyze current state of repository and dev dependencies
  • [x] Check current build/test/lint status (all passing)
  • [x] Update dev dependencies in groups to avoid breaking changes:
    • [x] Group 1: Minor version updates (safe updates)
      • [x] @eslint/js: 9.11.0 → 9.34.0
      • [x] @tailwindcss/typography: 0.5.15 → 0.5.16
      • [x] concurrently: 9.0.1 → 9.2.1
      • [x] eslint: 9.11.0 → 9.34.0
      • [x] husky: 9.1.6 → 9.1.7
      • [x] tsx: 4.19.1 → 4.20.5
      • [x] type-fest: 4.26.1 → 4.41.0
      • [x] typescript-eslint: 8.6.0 → 8.41.0
    • [x] Group 2: Potential breaking changes (needs careful testing)
      • [x] @sindresorhus/tsconfig: 6.0.0 → 8.0.1 (major version - required enum → const conversion)
      • [x] @types/node: 22.5.5 → 24.3.0 (major version - no breaking changes)
      • [x] globals: 15.9.0 → 16.3.0 (major version - no breaking changes)
      • [x] typescript: 5.6.2 → 5.9.2 (downgrade to latest stable - no breaking changes)
  • [x] Test build/lint/tests after each group update
  • [x] Fix any breaking changes that arise
    • [x] Converted enum to const object with proper TypeScript types due to erasableSyntaxOnly setting
  • [x] Final verification that all functionality works
    • [x] All tests pass (80/80)
    • [x] Build completes successfully
    • [x] Linting passes with no errors
    • [x] Dev server runs correctly

Summary of changes:

  • All dev dependencies updated to latest versions
  • One code change required: Converted enum Condition to const Condition with proper TypeScript types to comply with newer tsconfig settings that enable erasableSyntaxOnly
  • No breaking functionality changes: All tests pass, build works, linting passes
  • Development server confirmed working

The updates include many bug fixes, performance improvements, and new features from the dependency maintainers while maintaining full backward compatibility of the json-server functionality.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Copilot avatar Aug 30 '25 13:08 Copilot

id 1

derid149 avatar Sep 12 '25 15:09 derid149