Skip to content

Remove unused @types/js-yaml devDependency #48

Description

@pinecone-groundskeeper

Problem

package.json lists "@types/js-yaml": "^4" as a devDependency, but there is no js-yaml runtime dependency anywhere in package.json, and no import of js-yaml anywhere in src/ or tests/. A repo-wide search confirms js-yaml only appears in package.json/package-lock.json as this dangling types package — it is never actually used:

$ grep -rn "js-yaml" package.json src tests
package.json:56:    "`@types/js-yaml`": "^4",

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-yaml is removed from package.json devDependencies.
  • package-lock.json is regenerated (npm install) with the entry removed.
  • npm run typecheck and npm run lint still pass (nothing in src//tests/ references js-yaml types).

Scope

Remove only the unused @types/js-yaml devDependency and regenerate the lockfile. Do not touch any other dependency, and do not add a real js-yaml runtime dependency — if a future need for YAML parsing arises, that is a separate, deliberate addition.

Generated by GitHub Maintenance Audit · sonnet50 · 60.5 AIC · ⌖ 5.78 AIC · ⊞ 7.9K · ◷

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    agent:maintenance-auditFiled by the maintenance audit agent; it recognizes its own backlog by this labelmaintenanceIn scope for the maintenance agent

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions