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
When performing a server-side search using the Algolia client in a Next.js (App Router) environment, the application throws a warning due to the use of the deprecated url.parse() API (Node.js internal code DEP0169).
Set up an Algolia client using the "Backend Search" pattern in Next.js.
Call algoliaClient.search(requests) within a Server Action or a Server Component.
Trigger a search request.
The process terminates with DEP0169 uncaught exception.
Expected Behavior
The client should use the standard WHATWG URL API (new URL()) for URL parsing to comply with modern Node.js standards and avoid security implications as suggested by the Node.js core.
Actual Behavior
The client seems to be using url.parse(), which triggers a critical warning that, in certain strict environments or under specific Node.js configurations, results in an uncaughtException that crashes the dev server.
Client
Search
Version
algoliasearch@4.25.3
Relevant log output
> uncaughtException: DeprecationWarning: `url.parse()` behavior is not standardized and prone to errors that have security implications. Use the WHATWG URL API instead. at new Promise (<anonymous>) at async fetchResultsServer (./results.js:22:24) at async Object.search (./client.js:23:21)|| const response = await algoliaClient.search(requests);| code: 'DEP0169'
Activity
Haroenv commentedon Feb 17, 2026
You should use algoliasearch v5 which already has this fixed. You're using v4.
Compare v4:
algoliasearch-client-javascript/packages/requester-node-http/src/createNodeHttpRequester.ts
Line 32 in 4348b38
with v5:
algoliasearch-client-javascript/packages/requester-node-http/src/createHttpRequester.ts
Line 35 in 1c2c3e0
which no longer uses url.parse