"Unmet peer dependency" warning when installing plugin

Open
#296 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
node.js, typescript
Domain
cli, devops

Research direction

Reproduce the warning with sf plugins install devops-center, using the reported SFDX CLI 2.21.7 on macOS Sonoma 14.2. Inspect the installed plugin's dependency metadata, especially the ts-node peer dependencies on @types/node and TypeScript. Done means the cause is identified and the installation no longer reports these unmet peer dependencies, or the issue is documented as an upstream limitation.

Written by the indexing model from the issue text.

Description

I received the following response when installing the DevOps Center CLI plugin:

~ % sf plugins install devops-center 
Polling for new version(s) to become available on npm... done
Successfully validated digital signature for @salesforce/plugin-devops-center.
Finished digital signature check.
Installing plugin devops-center@latest... installed v1.2.5
 ›   Warning: "@salesforce/plugin-devops-center > @oclif/core > ts-node@10.9.2" has unmet peer dependency "@types/node@*".
 ›   Warning: "@salesforce/plugin-devops-center > @oclif/core > ts-node@10.9.2" has unmet peer dependency "typescript@>=2.7".

These warnings can only be addressed by the owner(s) of @salesforce/plugin-devops-center.
We suggest that you create an issue at https://github.com/forcedotcom/cli/issues and ask the plugin owners to address them.


Successfully installed @salesforce/plugin-devops-center v1.2.5

So I'm just following instructions from my computer overlord.

VS Code Version:
1.85.1
SFDX CLI Version:
2.21.7
OS and version:
macOS Sonoma 14.2

Dominant language
TypeScript
Stars
14
Forks
4
Avg merge
1m
Merged PRs (30d)
1

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 salesforcecli/plugin-devops-center

All issues in salesforcecli/plugin-devops-center

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.