Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions Frontend/.expo/README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
> Why do I have a folder named ".expo" in my project?
The ".expo" folder is created when an Expo project is started using "expo start" command.
> What do the files contain?
- "devices.json": contains information about devices that have recently opened this project. This is used to populate the "Development sessions" list in your development builds.
- "settings.json": contains the server configuration that is used to serve the application manifest.
> Should I commit the ".expo" folder?
No, you should not share the ".expo" folder. It does not contain any information that is relevant for other developers working on the project, it is specific to your machine.
Upon project creation, the ".expo" folder is already added to your ".gitignore" file.
Comment on lines +1 to +8
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Remove this file from the PR.

This README explicitly documents that the .expo folder "should not be shared" and "is already added to your .gitignore file" (line 7-8), yet you're committing it to the repository. This is inconsistent with Expo best practices.

🤖 Prompt for AI Agents
In Frontend/.expo/README.md lines 1-8: this file documents that the .expo folder
should not be shared yet the folder is being committed; remove the .expo folder
and its README from the PR, ensure .expo is listed in Frontend/.gitignore (or
the repo root .gitignore), and untrack any already committed .expo files by
running git rm -r --cached Frontend/.expo (or remove tracked files via your Git
client), then commit the removal and push; do not add any .expo content back
into the repo.

3 changes: 3 additions & 0 deletions Frontend/.expo/devices.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,3 @@
{
"devices": []
}
Comment on lines +1 to +3
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Do not commit the .expo folder.

The Frontend/.expo/README.md file added in this same PR explicitly states: "No, you should not share the '.expo' folder" and "Upon project creation, the '.expo' folder is already added to your '.gitignore' file." This contradicts the inclusion of these files in the PR.

Remove the .expo folder from this PR and ensure it's listed in .gitignore.

🤖 Prompt for AI Agents
In Frontend/.expo/devices.json around lines 1 to 3, the committed .expo folder
should not be included in the repo; remove the .expo directory from the PR and
ensure it is ignored: delete the .expo files from the commit (use git rm
--cached -r Frontend/.expo or remove and re-commit without them), add or confirm
Frontend/.gitignore contains an entry for /.expo or .expo/ (and commit that
change), and verify the .expo folder is no longer tracked (git status) before
pushing the updated branch.

106 changes: 103 additions & 3 deletions Frontend/package-lock.json

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

5 changes: 4 additions & 1 deletion Frontend/package.json
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,10 @@
"react-native-toast-message": "^2.2.1",
"react-native-vector-icons": "^10.2.0",
"react-navigation": "^4.4.4",
"react-navigation-bottom-tabs": "^1.0.2"
"react-navigation-bottom-tabs": "^1.0.2",
"react-dom": "18.3.1",
"react-native-web": "~0.19.13",
"@expo/metro-runtime": "~4.0.1"
Comment on lines +46 to +48
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Search for usage of the newly added dependencies in Frontend directory
echo "=== Searching for react-dom imports ==="
rg -n "from ['\"]react-dom['\"]|import.*react-dom|require\(['\"]react-dom['\"]\)" Frontend/ --type=js --type=jsx --type=ts --type=tsx 2>/dev/null || echo "No react-dom imports found"

echo -e "\n=== Searching for react-native-web imports ==="
rg -n "from ['\"]react-native-web['\"]|import.*react-native-web|require\(['\"]react-native-web['\"]\)" Frontend/ --type=js --type=jsx --type=ts --type=tsx 2>/dev/null || echo "No react-native-web imports found"

echo -e "\n=== Searching for @expo/metro-runtime imports ==="
rg -n "from ['\"]@expo/metro-runtime['\"]|import.*@expo/metro-runtime|require\(['\"]@expo/metro-runtime['\"]\)" Frontend/ --type=js --type=jsx --type=ts --type=tsx 2>/dev/null || echo "No @expo/metro-runtime imports found"

echo -e "\n=== Checking Frontend/package.json for context ==="
cat Frontend/package.json 2>/dev/null | head -60

Repository: AOSSIE-Org/BabyNest

Length of output: 2516


🏁 Script executed:

#!/bin/bash
# Check for build configuration files that might use these packages
echo "=== Looking for metro/webpack/build config files ==="
fd -e "metro.config.js" -e "webpack.config.js" -e "expo.json" -e "app.json" -e "babel.config.js"

echo -e "\n=== Checking if there's a web subdirectory or web-specific project ==="
find . -maxdepth 2 -type d \( -name "web" -o -name "Web" -o -name "www" \) 2>/dev/null

echo -e "\n=== Checking repo root structure ==="
ls -la | head -20

echo -e "\n=== Checking for any Expo or web configuration in Frontend ==="
cat Frontend/babel.config.js 2>/dev/null || echo "No babel.config.js"

Repository: AOSSIE-Org/BabyNest

Length of output: 1527


🏁 Script executed:

#!/bin/bash
# Check git history to see if these dependencies were newly added or already present
echo "=== Checking git history for these dependencies ==="
git log --oneline -20 -- Frontend/package.json

echo -e "\n=== Checking if these packages were added recently ==="
git diff HEAD~1 Frontend/package.json 2>/dev/null | grep -A 2 -B 2 "react-dom\|react-native-web\|@expo/metro-runtime" || echo "Unable to compare with previous commit"

echo -e "\n=== Checking current branch/PR info ==="
git status

Repository: AOSSIE-Org/BabyNest

Length of output: 581


🏁 Script executed:

#!/bin/bash
# Get the detailed diff of the most recent commit for package.json
echo "=== Checking the most recent commit diff for Frontend/package.json ==="
git show f0b5245:Frontend/package.json 2>/dev/null | tail -20

echo -e "\n=== Checking the actual diff of what changed ==="
git show f0b5245 -- Frontend/package.json 2>/dev/null | head -100

Repository: AOSSIE-Org/BabyNest

Length of output: 3753


Remove unused Expo web dependencies from package.json.

The dependencies react-dom, react-native-web, and @expo/metro-runtime added in this PR are not imported anywhere in the codebase and are incompatible with this React Native mobile-only project. There is no web build configuration (no metro.config.js, webpack.config.js, or expo.json), no web platform targets, and no justification for these packages. Since the PR is focused on improving behavior when the AI agent is unavailable, these unrelated dependencies should be removed.

🤖 Prompt for AI Agents
In Frontend/package.json around lines 46 to 48, remove the unused Expo/web
dependencies "react-dom", "react-native-web", and "@expo/metro-runtime" because
they are not imported anywhere, incompatible with this mobile-only React Native
project, and there is no web build config; update package.json by deleting these
three entries and then run npm/yarn install to update the lockfile and ensure no
residual references remain.

},
"devDependencies": {
"@babel/core": "^7.25.2",
Expand Down
Loading