Skip to content

chore(deps): bump exa-js from 1.10.3 to 2.13.0 in /backend #907

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.

Sign up for GitHub

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

Closed
dependabot wants to merge 1 commit into from
Closed

chore(deps): bump exa-js from 1.10.3 to 2.13.0 in /backend #907

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
2 changes: 1 addition & 1 deletion backend/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@
"dotenv": "^17.2.3",
"drizzle-orm": "^0.45.2",
"elysia": "^1.4.28",
"exa-js": "^1.0.11",
"exa-js": "^2.13.0",

@cursor cursor Bot May 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Search fetches unnecessary page contents by default in v2

High Severity

Bumping exa-js from v1 to v2 changes the default behavior of search() to include page contents ({ text: { maxCharacters: 10_000 } }) with every result. The search endpoint in search.ts only uses metadata (url, title, image, favicon) and discards all text content. This means every search now fetches up to 10,000 characters per result unnecessarily, significantly increasing latency and API costs. The search() call needs contents: false to restore the previous metadata-only behavior.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 29b1a1f. Configure here.

@cursor cursor Bot May 27, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Removed useAutoprompt option breaks search call in v2

Medium Severity

The useAutoprompt option passed in the search() call was deprecated and removed from exa-js v2's search options. Bumping to v2.13.0 makes this parameter either a TypeScript compilation error (if the type no longer accepts it) or silently ignored dead code. Either way, the intended autoprompt behavior is no longer being applied to searches.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 29b1a1f. Configure here.

"ipaddr.js": "^2.3.0",
"jose": "^6.2.2",
"openai": "^6.34.0",
Expand Down
Loading