pnpm i: WARN Issues with peer dependencies found
See original GitHub issueI have some issues with pnpm run dashboard:start
(see https://github.com/platformatic/platformatic/issues/228), so I have tried to clean my local installation executing some commands as documented in CONTRIBUTING.md:
pnpm run cleanall
pnpm i
but at the end I have got some warnings: “WARN Issues with peer dependencies found”
Below the full output:
ricfio@LENOVO:~/projects/platformatic/platformatic$ pnpm run cleanall
> platformatic@0.4.0 cleanall /home/ricfio/projects/platformatic/platformatic
> rm pnpm-lock.yaml && rm -rf node_modules && rm -rf packages/*/node_modules
ricfio@LENOVO:~/projects/platformatic/platformatic$ pnpm i
Scope: all 13 workspace projects
packages/db-dashboard | WARN deprecated querystring@0.2.0
Packages: +978
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Packages are hard linked from the content-addressable store to the virtual store.
Content-addressable store is at: /home/ricfio/.local/share/pnpm/store/v3
Virtual store is at: node_modules/.pnpm
Progress: resolved 999, reused 977, downloaded 0, added 978, done
. postinstall$ node ./scripts/postinstall.js
[32 lines collapsed]
│ build/assets/forEachState.es.2bb545d4.js 0.22 KiB / gzip: 0.20 KiB
│ build/assets/jump.es.ae3b5de5.js 2.88 KiB / gzip: 1.21 KiB
│ build/assets/mode.es.9fd5aa43.js 0.77 KiB / gzip: 0.51 KiB
│ build/assets/hint.es2.f63e46dc.js 3.06 KiB / gzip: 1.35 KiB
│ build/assets/lint.es2.183e4ef4.js 4.59 KiB / gzip: 2.05 KiB
│ build/assets/mode.es3.11ee0649.js 1.71 KiB / gzip: 0.91 KiB
│ build/assets/mode.es2.9565f44c.js 1.59 KiB / gzip: 0.84 KiB
│ build/assets/codemirror.es.3479d3c3.js 179.60 KiB / gzip: 60.84 KiB
│ build/assets/index.95357877.css 775.49 KiB / gzip: 323.90 KiB
│ build/assets/index.e377d3c1.js 2592.52 KiB / gzip: 772.87 KiB
└─ Done in 27.4s
dependencies:
+ desm 1.3.0
devDependencies:
+ @fastify/pre-commit 2.0.2
WARN Issues with peer dependencies found
packages/db-dashboard
├─┬ graphiql 2.0.10
│ └─┬ @graphiql/react 0.13.4
│ ├─┬ @reach/combobox 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ ├── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ ├─┬ @reach/auto-id 0.17.0
│ │ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ │ ├── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ │ └─┬ @reach/utils 0.17.0
│ │ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ ├─┬ @reach/descendants 0.17.0
│ │ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ └─┬ @reach/popover 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ ├── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ ├─┬ @reach/portal 0.17.0
│ │ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ └─┬ @reach/rect 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ ├─┬ @reach/dialog 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ ├─┬ @reach/listbox 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ ├── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ └─┬ @reach/machine 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ ├─┬ @reach/menu-button 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ ├── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ │ └─┬ @reach/dropdown 0.17.0
│ │ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ │ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ └─┬ @reach/tooltip 0.17.0
│ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ ├── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
│ └─┬ @reach/visually-hidden 0.17.0
│ ├── ✕ unmet peer react@"^16.8.0 || 17.x": found 18.2.0
│ └── ✕ unmet peer react-dom@"^16.8.0 || 17.x": found 18.2.0
└─┬ swagger-ui-react 4.13.0
├─┬ react-copy-to-clipboard 5.0.4
│ └── ✕ unmet peer react@"^15.3.0 || ^16.0.0 || ^17.0.0": found 18.2.0
├─┬ react-debounce-input 3.2.4
│ └── ✕ unmet peer react@"^15.3.0 || ^16.0.0 || ^17.0.0": found 18.2.0
└─┬ react-inspector 5.1.1
└── ✕ unmet peer react@"^16.8.4 || ^17.0.0": found 18.2.0
Done in 47.9s
Issue Analytics
- State:
- Created a year ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
missing peer dependencies after installation of pnpm v6.24.4
pnpm version: 6.24.4 Code to reproduce the issue: pnpm add [npm package] eg ... + lauqe 1.5.0 WARN Issues with peer dependencies found...
Read more >How peers are resolved - PNPM
Peer dependencies are resolved from dependencies installed higher in the dependency graph, since they share the same version as their parent. That means...
Read more >pnpm peer dependencies auto-install - Stack Overflow
hint: If you don't want pnpm to fail on peer dependency issues, set the "strict-peer-dependencies" setting to "false". auto-install-peers = true.
Read more >if you don't want pnpm to fail on peer dependency issues, add ...
Peer dependencies are resolved from dependencies installed higher in the dependency graph, since they share the same version as their parent. That means...
Read more >Pnpm doesn't auto install peer dependencies ... - Hacker News
Peer dependencies added more problems than they solved in my eyes... Most peer dependencies warnings come because some maintainer forgot to update the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Everything works, don’t worry too much about this.
@leorossi @marcopiraccini could one of you take a look at this too? I think we are running on a few old dependencies here.