Replies: 1 comment
-
Hi there, Not sure if you're still having this issue, but looking at how the CLI resolves package dependencies Lines 116 to 121 in b545938 you can fix this by including @capacitor/motion in your packages as a dependency or devDependency. I personally went the devDependency route, as really, we only require the package at build (or dev) time.
I think this feels like an inappropriate fix as that plugin is definitely needed at runtime, but would otherwise be included automagically at build time if the CLI could analyze transitive dependencies. Perhaps |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hey,
I have a wrapper (
MyWrapper
) for a capacitor plugin (@capacitor/motion) that has @capacitor/motion as a dependency. I want the @capacitor/motion plugin to be added when I addMyWrapper
to the dependencies of my app, but whenever I runnpx cap sync
the plugin is not detected.If I add
@capacitor/motion
to the package.json of my app, it works fine.Is there a way so I can indicate that
MyWrapper
has a capacitor plugin as a dependency?Kind regards,
Maxim
Beta Was this translation helpful? Give feedback.
All reactions