Specify peer dependency version

Open
#947 0 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript, nodejs
Domain
tooling

Research direction

Start with package.json and read the linked npm package.json documentation, then review debug issue 912 for the dependency context. Compare the existing peerDependenciesMeta entry with the documented peer dependency structure and determine the intended supports-color compatibility. Done means the repository has a confirmed dependency configuration and any relevant validation passes.

Written by the indexing model from the issue text.

Description

Currently the package.json has this section:

"peerDependenciesMeta": {
    "supports-color": {
      "optional": true
    }
  },

but there is no peerDependencies defined there at all. Am I missing or peerDependenciesMeta should be used in combination with peerDependencies as described in the docs? How is this supposed to work?

The reason why I am asking is this issue. Wouldn't that be fixed by just adding peerDependencies and specifying supports-color as <= 8?

Dominant language
JavaScript
Stars
11.5k
Forks
992
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from debug-js/debug

All issues in debug-js/debug

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.