Difficulty: Hard
Type: Maintenance
Summary
Clean up package.json so dependency metadata is valid, unambiguous, and safe for package tooling.
Current Behaviour
package.json contains two dependencies objects. JSON parsers typically keep the later key and ignore the earlier one, which can hide dependency changes and confuse maintainers.
Expected Behaviour
The package manifest should contain a single dependencies block with all runtime dependencies listed once.
Suggested Implementation
Merge the duplicate dependencies entries into one block. Add a package metadata validation step to CI so duplicate keys or malformed package metadata are caught before release.
Files or Areas Likely Affected
package.jsonpnpm-lock.yaml.github/workflows/README.md
Acceptance Criteria
Additional Notes
This is a small but important release-safety issue because npm publishing relies on correct package metadata.
Difficulty: Hard
Type: Maintenance
Summary
Clean up
package.jsonso dependency metadata is valid, unambiguous, and safe for package tooling.Current Behaviour
package.jsoncontains twodependenciesobjects. JSON parsers typically keep the later key and ignore the earlier one, which can hide dependency changes and confuse maintainers.Expected Behaviour
The package manifest should contain a single
dependenciesblock with all runtime dependencies listed once.Suggested Implementation
Merge the duplicate
dependenciesentries into one block. Add a package metadata validation step to CI so duplicate keys or malformed package metadata are caught before release.Files or Areas Likely Affected
package.jsonpnpm-lock.yaml.github/workflows/README.mdAcceptance Criteria
package.jsoncontains only onedependenciesobjectAdditional Notes
This is a small but important release-safety issue because npm publishing relies on correct package metadata.