Keep feat-single-search backend updated as lightweight search API #868
Description
Is your feature request related to a problem? Please describe.
I am using Perplexica for backend/API purposes and need a lightweight search-only solution that doesn’t come bundled with frontend code. Currently, the main branch is tightly coupled with the Next.js frontend, which adds unnecessary complexity and dependencies for developers focused only on API/search integration. The feat-single-search branch, built with Node/Express, is better suited for backend/API workflows, but it is outdated and risks falling behind on critical features and fixes.
Describe the solution you'd like
Please keep the feat-single-search branch up to date with the latest backend improvements, or merge essential backend features from main into a new, maintained API-only branch. This would provide a dedicated, lightweight Node/Express implementation for developers who only need search functionality via API—without requiring Next.js or frontend dependencies.
Describe alternatives you've considered
- Using the current main branch, but it is bloated with frontend code and dependencies, making it inefficient for backend-only use cases.
- Manually building a wrapper for single-search API requests, which duplicates work already present in feat-single-search.
- Running the outdated feat-single-search branch directly, but this causes compatibility and maintenance issues.