Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Could not find dependency version for xxx
See original GitHub issueBug Report
Describe the bug
After running docz dev, I am seeing a lot of could not find dependency version for ... in my console. However, after the build process, the app still runs fine.
To Reproduce
I am assuming this bug comes from how I import my modules. I used resolved path to import my module, but Docz thinks it is a node module missing dependency version?
Expected behavior
Console should have no warnings.
Environment
- OS: 10.14.2
- Node/npm version: 10.12.0
Additional context/Screenshots
Issue Analytics
- State:
- Created 5 years ago
- Reactions:21
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Could not find dependency version for xxx · Issue #598 - GitHub
I am assuming this bug comes from how I import my modules. I used resolved path to import my module, but Docz thinks...
Read more >Maven Could not resolve dependencies, artifacts could not be ...
I've tried downloading the newest version of maven, and included it in the eclipse helios, but still the same problem. The same error...
Read more >Learning the Basics - Gradle User Manual
Gradle exposes an API to declare what a repository may or may not contain. There are different use cases for it: performance, when...
Read more >Commands | Documentation | Poetry - Python dependency ...
In order to get the latest versions of the dependencies and to update the poetry.lock file, you should use the update command. poetry...
Read more >Workspace setup throwing errors in spite of adding RAML ...
Workspace setup throwing errors in spite of adding RAML dependencies in the pom file. Added this dependency in POM file but still getting...
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 Free
Top 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
I solved the problem by using relative path in all of my
mdxfiles (you can use alias in your component source files, that’s fine, but if you use alias inmdxfiles, you will get this error, but it doesn’t cause any functional bugs)It happens on 1.1.0 some problem with alias