# Ionic/Angular client

**URL:** <https://discuss.elastic.co/t/ionic-angular-client/191097>\
**Category:** Elasticsearch\
**Created:** [July 17, 2019, 10:10pm UTC](https://discuss.elastic.co/t/ionic-angular-client/191097 "2019-07-17T22:10:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![crossmeister](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/crossmeister/32/50409_2.png) [@crossmeister](https://discuss.elastic.co/u/crossmeister)\
**Post date:** [July 17, 2019, 10:10pm UTC](https://discuss.elastic.co/t/ionic-angular-client/191097/1 "2019-07-17T22:10:53Z")

</div>

Hi,

First post, so please be gentle 😀

I'm currently evaluating Elasticsearch Cloud and am prototyping access from Ionic/Angular clients.

My understanding is that the new JavaScript client is solely for node.js and no longer supports browser access. Is this correct?

Is there an alternative library that supports browser access or shouldn't I even be considering this due to security concerns? Is a lightweight proxy a better approach or perhaps a Logstash endpoint supporting HTTP input (but I guess security concerns there too)?

Apologies if these are naive questions!

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [July 18, 2019, 12:41pm UTC](https://discuss.elastic.co/t/ionic-angular-client/191097/2 "2019-07-18T12:41:38Z")

</div>

Welcome!

I'd look at SearchUI: [Search UI Version 1.0.0 Released | Elastic Blog](https://www.elastic.co/fr/blog/search-ui-1-0-0-released)

This is working with App Search which is working on top of elasticsearch. So if you are after the "search" use case, I'd recommend using the App Search service instead of the Elasticsearch service.

But in case it does not fit your use case, here are some other answers:

> My understanding is that the new JavaScript client is solely for node.js

I don't think so but I'm not an expert on that language though 🙂  
If you read this: [Introduction | Elasticsearch JavaScript Client [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/client/javascript-api/current/introduction.html#_browser)

It says that:

> There is no official support for the browser environment. It exposes your Elasticsearch instance to everyone, which could lead to security issues. We recommend that you write a lightweight proxy that uses this client instead.

So to this question:

> shouldn't I even be considering this due to security concerns?

That makes a lot of sense not to expose elasticsearch directly IMHO.

HTH

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [August 15, 2019, 12:41pm UTC](https://discuss.elastic.co/t/ionic-angular-client/191097/3 "2019-08-15T12:41:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
