[Feedback]: Is `@types/elasticsearch` still under maintenance?

[xdewx]

Was the documentation helpful?

Yes

What documentation page is affected

types

Description

Some projects only require the types module. So, is there a plan to independently separate @elastic/elasticsearch/types?

[shainaraskas]

the package being referred to: https://www.npmjs.com/package/@types/elasticsearch

[xdewx]

https://www.npmjs.com/package/@types/elasticsearch

it seems too old and different from the latest api.

[shainaraskas]

sorry @xdewx - that was just a note for us to understand what you were referring to in your issue. we still need to investigate.

[szabosteve]

Hi @xdewx,

@types/elasticsearch was developed by a third party. It was useful when Elasticsearch-js didn’t have types, but that’s no longer the case. For this reason, it is no longer maintained, and currently, there is no plan from Elastic’s side to maintain it.

[xdewx]

Hi @xdewx,

@types/elasticsearch was developed by a third party. It was useful when Elasticsearch-js didn’t have types, but that’s no longer the case. For this reason, it is no longer maintained, and currently, there is no plan from Elastic’s side to maintain it.

I see. but what if user just wants to develop a lib which needs types only? in such scene, there will be many extra deps. anyway, it still works.