CORS issue with JS Client and Multi Parameters issue with TS Client. about weaviate-javascript-client

[kcm]

Hi, yes, HTTPS is generally required for most use today. You'll need to either use a local proxy or disable checks as you've found without it, generally.

The Typescript client works with both JS and TS. You should be be able to use either with React 18. Please give that a shot and see if your issues remain.

I'm going to close this issue as the client is no longer maintained.

[trengrj]

@D3SERT-Eagle,

Regarding the query for the TS client, you may be confusing Weaviate API key vs OpenAI keys. The below config will connect with a Weaviate API key and OpenAI key for the OpenAI module:

const weaviate = require('weaviate-ts-client');

// Instantiate the client with the auth config
const client = weaviate.client({
  scheme: 'https',
  host: "some-endpoint.weaviate.network",
  apiKey: new weaviate.ApiKey("YOUR-WEAVIATE-API-KEY"),  // Replace w/ your API Key for the Weaviate instance
  headers: {"X-OpenAI-Api-Key": "<THE-KEY>"}
});

For your questions around CORS. Currently the header X-OpenAI-Api-Key will not be allowed by the browser unless explicitly allowed via CORS due to browser security settings. We have an open issue to add custom CORS settings to Weaviate weaviate/weaviate#2486. A current workaround would be to use NGINX or create a simple wrapper api around Weaviate which would also give you the benefit of keeping the OpenAI key hidden from users.