Remove unused JavaScript code and clean up dependencies

[hawkeyexl]

Eliminate unnecessary JavaScript files and update package dependencies to their latest versions for improved performance and security.

Summary by CodeRabbit

• Chores

  • Updated development dependencies including TypeScript (^5.9.3) and Node types (^25.0.10), plus runtime libraries for schema operations and HTTP requests

• Refactor

  • Removed multiple core modules and significantly restructured the public API surface, requiring migration for existing implementations

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

This PR removes multiple core modules (validate.js, resolvePaths.js, files.js) and their public exports while updating dependency versions. It eliminates validation, path resolution, and file reading utilities from the public API surface and deletes a TypeScript migration planning document.

Changes

Cohort / File(s)	Summary
Dependency Updates package.json	Updated @types/node (^22.10.5 → ^25.0.10), typescript (^5.7.3 → ^5.9.3), @apidevtools/json-schema-ref-parser (^15.1.3 → ^15.2.2), and axios (^1.13.2 → ^1.13.4)
Planning Documentation plans/plan-typescriptMigration.prompt.md	Deleted TypeScript migration planning document (25 lines)
Core Module Removals src/validate.js, src/resolvePaths.js, src/files.js	Removed validation system with AJV integration (596 lines), path resolution utility (253 lines), and file reading utility (84 lines)
API Surface Changes src/index.js, src/schemas/index.js	Removed exports for validate, transformToSchemaKey, readFile, resolvePaths, and schemas from public API

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Possibly related PRs

• typescript migration: all source files, not including tests and build scripts #153: Adds TypeScript versions of the same modules (validate, transformToSchemaKey, resolvePaths, readFile, schemas) being removed here—direct code-level replacement.
• Update dependencies to latest versions #146: Modifies package.json dependency versions including @apidevtools/json-schema-ref-parser, overlapping with version bump changes.
• Enhance configuration and schema definitions #112: Extends resolvePaths.js with additional recognized path properties—conflicts with removal of the module.

Poem

🐰 Old JavaScript bids farewell,
TypeScript's embrace casts its spell,
Validation, paths, and files gone,
Migration marches boldly on! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main changes: removing unused JavaScript code (files.js, resolvePaths.js, validate.js, index.js export removals) and updating package.json dependencies.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Copilot]

Pull request overview

This PR aims to complete a TypeScript migration by removing obsolete JavaScript source files and updating package dependencies. The JavaScript files (validate.js, resolvePaths.js, files.js, schemas/index.js, and index.js) are being deleted as they have been replaced with TypeScript equivalents that compile to the dist/ directory.

Changes:

• Removed 5 JavaScript source files that have been migrated to TypeScript
• Deleted TypeScript migration planning document
• Updated multiple package dependencies to newer versions

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/validate.js	Deleted 596-line validation module (replaced by validate.ts)
src/schemas/index.js	Deleted schema exports module (replaced by schemas/index.ts)
src/resolvePaths.js	Deleted 253-line path resolution module (replaced by resolvePaths.ts)
src/index.js	Deleted main entry point (replaced by index.ts)
src/files.js	Deleted 84-line file reading module (replaced by files.ts)
plans/plan-typescriptMigration.prompt.md	Removed completed migration planning document
package.json	Updated 4 dependency versions
package-lock.json	Updated lockfile with new dependency versions and transitive dependencies

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

TypeScript version is being downgraded from 5.7.3 to 5.9.3. This appears to be a mistake as 5.7.3 is a newer version than 5.9.3. The PR description states dependencies should be updated to their latest versions for improved performance and security, but this change downgrades TypeScript instead. Consider updating to the latest TypeScript 5.x version (or keeping 5.7.3).

Suggested change

	"typescript": "^5.9.3"
	"typescript": "^5.7.3"

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@package.json`:
- Around line 37-43: The package.json currently depends on "@types/node" version
25 but the project lacks an explicit Node target; add an engines.node field in
package.json (or add a .nvmrc) to declare the supported Node.js version that
matches `@types/node` (or downgrade `@types/node` if you must support an older
Node), then update CI configs if present to use that Node version; ensure the
symbol "@types/node" in package.json aligns with the declared engines.node value
so TypeScript/tsconfig and runtime Node are consistent.

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Check for declared Node versions across the repo
echo "=== Checking package.json engines field ==="
rg -A 2 '"engines"' package.json

echo -e "\n=== Checking for .nvmrc, .node-version, .tool-versions ==="
fd -H '\.(nvmrc|node-version|tool-versions)$' -x cat {}

echo -e "\n=== Checking GitHub Actions workflows for Node setup ==="
fd -t f '\.github/workflows' -e yml -e yaml -x grep -l 'setup-node\|node-version' {} 2>/dev/null
if [ $? -eq 0 ]; then
  fd -t f '\.github/workflows' -e yml -e yaml -x grep -A 2 -B 2 'setup-node\|node-version' {} \;
fi

echo -e "\n=== Current package.json Node type/version references ==="
cat -n package.json | grep -i "node\|engine"

Repository: doc-detective/common

Length of output: 603

---

🌐 Web query:

TypeScript 5.9.3 minimum supported Node.js version requirements

💡 Result:

TypeScript 5.9.3 declares Node.js >= 14.17 as its minimum supported version via the engines.node field in its published package.json. [1] (This same requirement is also reflected in lockfile metadata that records [email protected] as engines: { node: '>=14.17' }.) [2]

Sources: [1] [2]

---

🌐 Web query:

@types/node 25.0.10 compatibility requirements and minimum Node.js version

💡 Result:

Web search failed: Server error: no LLM provider could handle the message

---

🌐 Web query:

@types/node 25.0 release minimum Node.js version compatibility

💡 Result:

@types/[email protected] is the type definition set aligned to Node.js v25.x (i.e., it describes APIs available in Node 25). (app.unpkg.com)

There is no “minimum Node.js version” enforced by the package itself (it’s types-only and its package.json does not declare an engines.node requirement), but for correctness you should use it when targeting/running on Node 25.x; otherwise you may get types for APIs that don’t exist in your runtime. (app.unpkg.com)

Citations:

• 1: https://app.unpkg.com/%40types/node%4025.0.0/files/package.json
• 2: https://app.unpkg.com/%40types/node%4025.0.0/files/package.json

---

Declare the target Node.js version and ensure @types/node 25 alignment.

The project lacks a declared Node version (engines.node in package.json, .nvmrc, or CI configuration). While TypeScript 5.9.3 supports Node ≥14.17, @types/node 25 is designed for Node.js v25.x APIs. If the project targets an older Node version, using @types/node 25 will expose type definitions for APIs that don't exist in your runtime, causing type mismatches. Add an explicit Node version declaration and verify @types/node 25 is appropriate for your target runtime.

🤖 Prompt for AI Agents

In `@package.json` around lines 37 - 43, The package.json currently depends on
"@types/node" version 25 but the project lacks an explicit Node target; add an
engines.node field in package.json (or add a .nvmrc) to declare the supported
Node.js version that matches `@types/node` (or downgrade `@types/node` if you must
support an older Node), then update CI configs if present to use that Node
version; ensure the symbol "@types/node" in package.json aligns with the
declared engines.node value so TypeScript/tsconfig and runtime Node are
consistent.