Cannot resolve dependency with @component

[joshleblanc]

This 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.

[robokozo]

I also get a similar error.

[wojtek-krysiak]

I've just published 1.3.3 version - please check it out - it should fix this (unfortunately I don't have Windows to check it out)

[robokozo]

I tried it again and got a different error with the new version.

[robokozo]

I think one possible issue is this line in bundler.js

require('path').posix

[DomenicRoti]

I just want to add I'm experiencing this as well on (on a mac), this is using @component in a vue/webpack project.

[hellhoundsx]

A bit of a stretch but for future guys passing through

@DomenicRoti you need to setup aliases on your .babelrc:
add this package to your project babel-plugin-module-resolver

and your .babelRC should look like(ignore the react-hot-loader):

[malikalimoekhamedov]

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?