Could a dependency conflict provide a little more detail?
See original GitHub issueA dependency conflict currently displays this information …
<PATH>\project.json(42,30): warning NU1012: Dependency conflict.
NETStandard.Platform 1.0.0-rc3-23901 expected System.AppContext >= 4.1.0-rc3-23901 but got
4.1.0-rc3-23829
Could this information also state which package (or packages) requested the lower version?
btw- Nit … “but got” … perhaps “but received” would be better.
Issue Analytics
- State:
- Created 8 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Could a dependency conflict provide a little more detail?
guardrex : https://github.com/dotnet/cli/issues/1646 A dependency conflict currently displays this information ... \project.json(42,30): ...
Read more >java - Maven dependency resolution (conflicted)
Maven can handle both situations without any conflict. Conflicts will exist when two versions of a transitive dependency are required.
Read more >[Resolved] NPM error - Fix the upstream dependency conflict
To fix this error, we can use the --legacy-peer-deps flag, find the conflicting package and downgrade or upgrade the relevant packages in our...
Read more >How to identify and resolve a dependency conflict
Find Divio's how-to guide to identifying and resolving a dependency conflict. Learn what steps to take if a deployment in the cloud or...
Read more >Watchman: monitoring dependency conflicts for Python library ...
Dependency conflict issues arise in theory when all of the constraints for a project and its dependencies cannot be simulataneously satisified.
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
I would really like it if a --verbose option told me why a package got a version it did not expect. This would hopefully save me from rummaging through the lock file.
Moving this to the nuget repo: https://github.com/NuGet/Home/issues/2238