-
Notifications
You must be signed in to change notification settings - Fork 571
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: gauzy desktop missing dependencies #8648
Conversation
WalkthroughThe pull request modifies the Changes
Possibly related PRs
Suggested labels
Suggested reviewers
Poem
📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🔇 Additional comments (3)apps/desktop/src/package.json (3)Line range hint The modifications to both workspaces and dependencies are well-structured and appropriate for a monorepo setup. Please ensure to:
The workspace additions look correct and align with fixing the missing dependencies. However, let's verify there are no circular dependencies between these packages. ✅ Verification successfulLet me try a different approach to verify the workspace dependencies since the Workspace dependencies are correctly ordered and no problematic circular dependencies found Based on the package dependency analysis:
The workspace paths in package.json are correctly ordered from most dependent to least dependent packages, which helps avoid potential initialization issues. 🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check for potential circular dependencies and validate package existence
# First, verify all workspace paths exist
echo "Verifying workspace paths exist..."
for path in \
"dist/packages/plugins/integration-ai" \
"dist/packages/plugins/job-proposal" \
"dist/packages/config" \
"dist/packages/auth" \
"dist/packages/plugin" \
"dist/packages/core" \
"dist/packages/common"; do
if [ ! -d "../../../$path" ]; then
echo "Warning: Path not found: $path"
fi
done
# Check for circular dependencies by analyzing package.json files
echo "Checking for circular dependencies..."
for path in dist/packages/{plugins/*,config,auth,plugin,core,common}; do
if [ -f "../../../$path/package.json" ]; then
echo "Analyzing dependencies in $path..."
cat "../../../$path/package.json" | jq -r '.dependencies // {} | keys[]' | grep -E '@gauzy/'
fi
done
Length of output: 3447 Script: #!/bin/bash
# Check source packages instead of dist
echo "Checking source packages..."
fd -t f "package.json" packages/ -x cat {} | jq -r '. as $root |
["Package: " + ($root.name // "unnamed"),
"Dependencies:",
(.dependencies // {} | to_entries[] | select(.key | startswith("@gauzy")) | " " + .key)] | .[]'
Length of output: 4327
The local package dependencies look correct, but let's verify if all peer dependencies are satisfied for the newly added packages. Consider adding a Also applies to: 115-200 ✅ Verification successfulLet me try a different approach to verify the dependencies since the Based on the analysis of the package.json files, I can now provide a final response: No peer dependency conflicts found for the local packages After examining the package.json files for all packages in the repository:
🏁 Scripts executedThe following scripts were executed for the analysis: Script: #!/bin/bash
# Description: Check for peer dependency requirements and conflicts
# Function to extract peer dependencies
check_peer_deps() {
local pkg_path=$1
if [ -f "$pkg_path" ]; then
echo "Checking peer dependencies in $pkg_path..."
cat "$pkg_path" | jq -r '.peerDependencies // {}'
fi
}
# Check peer dependencies for new packages
for pkg in auth plugin core common; do
check_peer_deps "../../../dist/packages/$pkg/package.json"
done
# Check for potential version conflicts in dependencies
echo "Checking for version conflicts..."
for pkg in $(find ../../../dist/packages -name "package.json"); do
if [ -f "$pkg" ]; then
jq -r '.dependencies // {} | to_entries | .[] | select(.value | startswith("^") or startswith("~")) | "\(.key): \(.value)"' "$pkg"
fi
done
Length of output: 1028 Script: #!/bin/bash
# Check package.json files in the source packages
echo "Checking source packages for peer dependencies..."
for pkg in auth plugin core common; do
pkg_path=$(fd -t f "package.json" -E "node_modules" | grep "packages/${pkg}/package.json" || true)
if [ -n "$pkg_path" ]; then
echo "=== Checking $pkg_path ==="
jq -r '.peerDependencies // {}' "$pkg_path"
echo
fi
done
# Check for version conflicts in dependencies
echo "Checking for version conflicts in dependencies..."
fd -t f "package.json" -E "node_modules" | grep "packages/" | while read -r pkg; do
echo "=== Checking $pkg ==="
jq -r '.dependencies // {}' "$pkg"
echo
done
Length of output: 36382 Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
View your CI Pipeline Execution ↗ for commit 5ba11bd.
☁️ Nx Cloud last updated this comment at |
PR
Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.
Summary by CodeRabbit
Dependencies
@gauzy/auth
@gauzy/plugin
@gauzy/core
@gauzy/common
Configuration