Cannot resolve dependency with @component
See original GitHub issueThis is probably a windows issue. Trying to use the @component tag results in this in entry.js
import Wrapper from '..\node_modules\better-docs\lib\react-wrapper.js';
That should be
import Wrapper from '../node_modules/better-docs/lib/react-wrapper.js';
The imports for the components have the same problem.
Issue Analytics
- State:
- Created 4 years ago
- Comments:7 (1 by maintainers)
Top Results From Across the Web
Parcel outputs "cannot resolve dependency" when building ...
The error you're getting seems to indicate that there is an import statement in src/App.ts that tries to reference a file called src/ ......
Read more >Learning the Basics - Gradle User Manual
Gradle can resolve dependencies from one or many repositories based on Maven, ... Origin of artifacts cannot be tracked, which is a correctness...
Read more >Dependency injection in action - Angular
When a component requests a dependency, Angular starts with that component's injector and walks up the injector tree until it finds the first...
Read more >Cannot Resolve Dependency to Assembly Error Occurs
Environment. Product · Description. An error that the dependency to a Telerik assembly cannot be resolved occurs. · Error Message. Cannot resolve dependency...
Read more >Module not found: Can't resolve 'styled-components'
To solve the error "Module not found: Error: Can't resolve 'styled-components'", make sure to install the styled-components package by opening your terminal ...
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 just want to add I’m experiencing this as well on (on a mac), this is using @component in a vue/webpack project.
Why was this issue closed? It’s still alive and well. The aforementioned hack is not really applicable to create-react-app based projects isn’t it? We don’t really have access to custom webpack configurations unless we eject. Or am I missing something?