You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
▲ 💊 Capgo Doctor 💊
│
● App Name:
│
● App ID:
│
● App Version: 0.0.0
│
● Web Dir:
│
● OS: darwin Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64
│
● Node: v20.13.1
│
● Installed Dependencies:
│
● @capgo/cli: 4.20.7
│
◇ Latest Dependencies:
│
● @capgo/cli: 4.20.7
│
◆ ✅ All dependencies are up to date
Current Behavior
Consider a nx monorepo with one package.json (and node_modules) in the root folder and the actual app residing in apps/my-app. The app itself does not have a package.json, because dependencies are shared in the monorepo.
Capacitor itself supports nx and has functions to find the correct package.json in the root path. However, if I run npx @capgo/cli bundle upload it complains, that no package.json exist.
If I create a dummy package.json, the command runs, but then cap commands fail, because the capacitor plugins are in the root node_modules folder and thus no plugins are added on the native side.
Since it works with a dummy package.json, there seems nothing important to be read from package.json, so why is it necessary at all?
Expected Behavior
It should be aligned with capacitor in monorepos and run successfully in nx environments.
The text was updated successfully, but these errors were encountered:
Bug Report
Capacitor Version
Plugin Version
Current Behavior
Consider a nx monorepo with one package.json (and node_modules) in the root folder and the actual app residing in
apps/my-app
. The app itself does not have a package.json, because dependencies are shared in the monorepo.Capacitor itself supports nx and has functions to find the correct package.json in the root path. However, if I run
npx @capgo/cli bundle upload
it complains, that no package.json exist.If I create a dummy package.json, the command runs, but then
cap
commands fail, because the capacitor plugins are in the root node_modules folder and thus no plugins are added on the native side.Since it works with a dummy package.json, there seems nothing important to be read from package.json, so why is it necessary at all?
Expected Behavior
It should be aligned with capacitor in monorepos and run successfully in nx environments.
The text was updated successfully, but these errors were encountered: