Issues using { Client }

[mperu92]

Hi, i'm trying to use the es client with Es6 + React, for connect my app into the elastic cloud using the code from the examples:
import { Client } from '@elastic/elasticsearch'; const client = new Client({ cloud: { id: 'Cloud-Name:Cloud-Id', username: 'elastic', password: 'my-password' } });

But when i launch the program it takes me this error

[ConnectionPool.js:375] Uncaught TypeError: URL is not a constructor

what could be the issue?

[delvedor]

Hello!
Are you using the client in the browser?

[mperu92]

yes, i'im

Hello!
Are you using the client in the browser?

Yes @delvedor, i'm using React client-side
(are you italian? Really? :))

[delvedor]

Yes @delvedor, i'm using React client-side

This client is not intended to be used in a browser environment.
Contact Elasticseach directly from the browser exposes you to many security risks and we do not support that.

(are you italian? Really? :))

Yes.

[mperu92]

Ah, ok thanks for this information.
I will try other ways.
(i'm tryng to build an Autocomplete widget with React and Elastic Search)

[delvedor]

(i'm tryng to build an Autocomplete widget with React and Elastic Search)

In this case, I suggest you take a look at elastic/search-ui

If you want to build your own system, I recommend you to put a simple Node.js server (which uses this client) between your React app and Elasticsearch.

[mperu92]

If you want to build your own system, I recommend you to put a simple Node.js server (which uses this client) between your React app and Elasticsearch.

Wow, thank you so much!
There is some documentation about this specific case?

[mperu92]

Because i haven't an Elastic App Search

[mperu92]

Solved really fast working server-side!

[delvedor]

Hello!
I'm closing this since it seems you have solved your issue. Please open a new issue if you have more questions! :)

[mperu92]

Hi thank you so much and sorry i forget to close it! Il giorno ven 26 apr 2019 alle ore 10:48 Tomas Della Vedova < notifications@github.com> ha scritto:

…

Closed #814 <#814>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#814 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AJEBVOLWWO6ESQC3DIOGOZ3PSK6U7ANCNFSM4HFOKYHA> .

[arunesh90]

It seems like this issue also occurs in Cloudflare's workers, any way to work around it?

[travis-r6s]

@arunesh90 I don't suppose you found the issue with this?

[tdossett]

What was the solution for this issue ?

[travis-r6s]

@tdossett I couldn't get it to work, so I just used the es rest api with fetch/exios etc.

[tdossett]

I see i was thinking about doing the same thing since elasticsearch.js using { Client } does not work yet.

THX do you have sample fetch, axios example ?

[travis-r6s]

Pulled from a quick workers & graphql demo app:

const endpoint = `${endpoint}/_search`
const credentials = new Buffer.from(`${username}:${password}`).toString('base64')

module.exports = {
  SearchResult: {
    __resolveType(obj, context, info){
      if (obj.first_name) return 'Contact'
      if (obj.name) return 'Company'
      return null
    },
  },
  Query: {
    search: async (parent, { query }, ctx, info) => {
      try {
        const queryBody = {
          multi_match: {
            query,
            fields: ['*_name^3', 'company'],
            fuzziness: 'AUTO'
          }
        }
        const response = await fetch(endpoint, {
          method: 'POST',
          headers: {
            'Accept': 'application/json',
            'Content-Type': 'application/json',
            'Authorization': `Basic ${credentials}`
          },
          body: JSON.stringify({ query: queryBody })
        })
        const data = await response.json()
        const results = data.hits.hits.map(hit => hit._source)
        return results
      } catch (error) {
        throw new Error(error.message)
      }
    }
  }
}

[tdossett]

Hi Travis, I ended up following your lead and did the following:  1. I used ‘axios’ to perform the https get request (normally I had ‘url’ and ‘auth’, but wanted to be more specific).  2. In my Elastic subscription I enable ‘cors’. AND NOW IT WORKS in Heroku …. Thank You Again 😊 …