feat:implemented the elasticsearch stack for the search

[Kavin-Bakyaraj]

No description provided.

[vercel]

@Kavin-Bakyaraj is attempting to deploy a commit to the Ibrahim's projects Team on Vercel.

A member of the Team first needs to authorize it.

[Marve10s]

Hey! Thank you for the PR! Will take a closer look soon

[Marve10s]

PR Review — Verified by Scaffolding + Type-Checking

I built the CLI from this branch, scaffolded real projects (elasticsearch + hono, elasticsearch + Next.js self, elasticsearch + express), installed dependencies, and ran tsc --noEmit on each.

---

3 Type Errors in search.ts.hbs

The generated search.ts fails type-checking with @elastic/elasticsearch@9.3.4 (resolved from the pinned ^9.1.0):

1. estypes.TypeMapping does not exist (line 182)

The correct type is MappingTypeMapping:

- mappings?: estypes.TypeMapping;
+ mappings?: estypes.MappingTypeMapping;

2. estypes.IndexSettings does not exist (line 183)

The correct type is IndicesIndexSettings:

- settings?: estypes.IndexSettings;
+ settings?: estypes.IndicesIndexSettings;

3. BulkResponseItem[] is not assignable from the SDK's actual return type (line 99/107)

The SDK returns Partial<Record<BulkOperationType, BulkResponseItem>>[], not BulkResponseItem[]:

- ): Promise<{ errors: boolean; items?: estypes.BulkResponseItem[] }> {
+ ): Promise<{ errors: boolean; items?: Partial<Record<estypes.BulkOperationType, estypes.BulkResponseItem>>[] }> {

---

What works well

• Scaffolding: All three test projects (hono, self/Next.js, express) scaffold correctly with the elasticsearch search helper, dependency, and env vars in the right locations
• self backend fix: This PR incidentally fixes a real bug — on main, self backends get the search dependency but no search.ts helper file. This fix benefits meilisearch and typesense too
• Env vars: The 5 elasticsearch env vars (node, cloud ID, API key, username, password) are well-documented with clear comments
• resolveConnection() logic: API key > basic auth > no auth priority, and Cloud ID > local node routing, are both correct
• Tests: 16 combo tests plus file content assertions provide solid coverage
• Web configurator: Icon, resource links, and constants are all properly wired

Minor notes

• ~30% of the diff is auto-formatter line wrapping changes (option-metadata.ts, schemas.ts, constant.ts) — consider splitting those into a separate commit
• PR body is empty — would be good to describe the feature and call out the self backend fix

Summary

Solid PR — just needs the 3 type fixes in the template and it should be good to go.

[Marve10s]

Small errors in templates Claude was able to find. Otherwise PR is very solid, I'd like to merge this after the fix. Thank you a lot!

[Kavin-Bakyaraj]

Small errors in templates Claude was able to find. Otherwise PR is very solid, I'd like to merge this after the fix. Thank you a lot!

sure, I will fix that ASAP