Relocate misplaced dependencies from `dependencies` to `devDependencies`

[rak-phillip]

Four packages are listed under dependencies in package.json but are only used at build or test time. Moving them to devDependencies correctly reflects their role and prevents them from being included in production installs.

Packages to move

• sinon — test mocking library
• babel-plugin-module-resolver — Babel plugin, build-time only
• cross-env — CLI tool used in npm scripts only
• ts-node — TypeScript runner for dev scripts

Acceptance criteria

• All packages listed above are in devDependencies
• CI passes all gates

[github-actions]

🎯 Agentic Issue Triage

This is a dependency hygiene task: move 4 packages currently listed under dependencies in package.json into devDependencies, as they are only needed at build/dev/test time and should not be bundled into production artifacts.

Confirmed misplaced packages (currently in dependencies):

• sinon — test mocking library (test-only)
• babel-plugin-module-resolver — Babel plugin, build-time only
• cross-env — CLI tool used only in npm scripts
• ts-node — TypeScript runner for dev/build scripts

This is a sub-issue of #17622 (Remove unused and misplaced dependencies).

📋 Implementation Checklist

• Move sinon from dependencies → devDependencies in package.json
• Move babel-plugin-module-resolver from dependencies → devDependencies
• Move cross-env from dependencies → devDependencies
• Move ts-node from dependencies → devDependencies
• Run yarn install --frozen-lockfile to verify no lock file conflicts (or update lock file if needed)
• Run yarn build to confirm production build still succeeds
• Run yarn test:ci to confirm unit tests still pass
• Run yarn lint to confirm no lint issues
• Mark checklist items in parent issue Remove unused and misplaced dependencies #17622 as complete

🔧 How to make the change

In package.json, locate each package under dependencies and move it to devDependencies. Example diff:

// Before
"dependencies": {
  "sinon": "x.y.z",
  "babel-plugin-module-resolver": "x.y.z",
  "cross-env": "x.y.z",
  "ts-node": "x.y.z",
  ...
}

// After — remove from dependencies, add to devDependencies
"devDependencies": {
  "sinon": "x.y.z",
  "babel-plugin-module-resolver": "x.y.z",
  "cross-env": "x.y.z",
  "ts-node": "x.y.z",
  ...
}

Per project guidelines, use yarn run upgrade:no-lock / yarn run add:no-lock only if adding new packages — here we're just moving existing entries, so a direct edit to package.json is appropriate.

⚠️ Potential Risks

• Moving cross-env could break any CI/npm script that runs in a production Docker image which does yarn install --production. Verify scripts only run in dev/CI contexts.
• Moving ts-node is safe as long as it is not dynamically required in runtime code. A quick grep confirms it's only used in build/config scripts.
• sinon is a test-only library — no runtime impact expected.
• babel-plugin-module-resolver is referenced in babel.config.js which is build-time only — safe to move.

🔍 Useful Commands for Verification

# Confirm no runtime source files import these packages
grep -r "require('sinon')\|from 'sinon'" shell/ pkg/ --include="*.ts" --include="*.js" --include="*.vue"
grep -r "require('ts-node')\|from 'ts-node'" shell/ pkg/ --include="*.ts" --include="*.js"
grep -r "cross-env" shell/ pkg/ --include="*.ts" --include="*.js" --include="*.vue"
grep -r "babel-plugin-module-resolver" shell/ pkg/ --include="*.ts" --include="*.js" --include="*.vue"

# After changes
yarn install
yarn build
yarn test:ci
yarn lint

Generated by Agentic Triage for issue #17623 · ● 182.6K · ◷

[github-actions]

🤖 Issue grooming analysis

This issue meets all four primary grooming criteria and is ready for triage.

Criterion	Status	Notes
Clear Problem Statement	✅	Clearly explains that four packages are listed under dependencies but are only used at build/test time; explains why this matters for production installs
Acceptance Criteria	✅	Checklist is concrete: all listed packages moved to devDependencies, CI passes all gates
Technical Details	✅	Each package is listed with a specific rationale (sinon — test mocking, babel-plugin-module-resolver — build-time, cross-env — npm scripts, ts-node — dev scripts)
Reproducibility	✅	Tech-debt task with clearly enumerated scope and specific target file (package.json)

This analysis was generated automatically based on the repository's grooming checklist.

Generated by Daily Issue Grooming · ● 584.1K · ◷