chore: remove unused cross-env dependency#4810
Conversation
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4810 +/- ##
=======================================
Coverage 93.30% 93.30%
=======================================
Files 14 14
Lines 5466 5466
Branches 793 793
=======================================
Hits 5100 5100
Misses 364 364
Partials 2 2 Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Summary
Removes the unused
cross-envdevelopment dependency and its orphaned transitive dependency frompackage-lock.json.cross-envwas added for the previousnyc-based coverage command in a01f01b. The coverage workflow was later migrated toc8in 47fc332, which removed the only usage ofcross-envwhile leaving the dependency declaration behind.No related issue; this is dependency cleanup.
What kind of change does this PR introduce?
chore
Did you add tests for your changes?
No. This change only removes unused dependency metadata and does not alter runtime behavior.
Validated that
cross-envand its orphaned transitive dependency are absent from both the manifest and lockfile.Does this PR introduce a breaking change?
No.
If relevant, what needs to be documented once your changes are merged or what have you already documented?
No documentation changes are needed.
Use of AI
Yes. I used Codex to audit dependency usage, inspect the Git history, identify the obsolete dependency and its orphaned transitive dependency, and validate the manifest and lockfile changes. I reviewed the resulting changes.