-
Notifications
You must be signed in to change notification settings - Fork 33
Remove unused @types/js-yaml devDependency #48
Copy link
Copy link
Open
Labels
agent:maintenance-auditFiled by the maintenance audit agent; it recognizes its own backlog by this labelFiled by the maintenance audit agent; it recognizes its own backlog by this labelmaintenanceIn scope for the maintenance agentIn scope for the maintenance agent
Description
Activity
Metadata
Metadata
Assignees
Labels
agent:maintenance-auditFiled by the maintenance audit agent; it recognizes its own backlog by this labelFiled by the maintenance audit agent; it recognizes its own backlog by this labelmaintenanceIn scope for the maintenance agentIn scope for the maintenance agent
Problem
package.jsonlists"@types/js-yaml": "^4"as a devDependency, but there is nojs-yamlruntime dependency anywhere inpackage.json, and no import ofjs-yamlanywhere insrc/ortests/. A repo-wide search confirmsjs-yamlonly appears inpackage.json/package-lock.jsonas this dangling types package — it is never actually used:This is dead scaffolding left over from an earlier version of the project (similar in kind to the leftover
turbo.json/library-publish scaffolding already cleaned up in issue #14) and adds unnecessary install weight and lockfile surface for no benefit.Acceptance criteria
@types/js-yamlis removed frompackage.jsondevDependencies.package-lock.jsonis regenerated (npm install) with the entry removed.npm run typecheckandnpm run lintstill pass (nothing insrc//tests/referencesjs-yamltypes).Scope
Remove only the unused
@types/js-yamldevDependency and regenerate the lockfile. Do not touch any other dependency, and do not add a realjs-yamlruntime dependency — if a future need for YAML parsing arises, that is a separate, deliberate addition.