PineconeClient: Project name not set. Call init() first

[ediardo]

Hi!

First day using Pinecone. I followed the steps at https://docs.pinecone.io/docs/node-client but I'm getting an error.

Version: 0.0.8

Code:

 const pinecone = new PineconeClient();
  await pinecone.init({
    environment: "us-east1-gcp",
    apiKey: "SECRET",
  });

  const index = pinecone.Index("websites");

  try {
    const res = await index.upsert({
      upsertRequest: {
        vectors: [
          {
            id: "1",
            values: vector,
          },
        ],
      },
    });
....

Error:

Error: PineconeClient: Project name not set. Call init() first.
    at PineconeClient.Index (./node_modules/@pinecone-database/pinecone/dist/index.js:172:19)
    at insertToVectorCollection (embeddings.js:50:28)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async createIndex (index.js:77:9)

I tried setting the projectName right before the init() but didn't make a difference:

const pinecone = new PineconeClient();
pinecone.projectName = "websites";
await pinecone.init({...

What can I do to fix problem?

Thank you.

[NCKLS]

I'm also receiving this error. It looks like I'm getting a
PineconeClient: Error getting project name: ReferenceError: fetch is not defined
error.

Quickly looking through the source code it seems it's trying to use the jsdom version of fetch and isn't using node-fetch or axios?

[JoshuaPerk]

+1

It looks like the PineconeClient.prototype.Index function checks for an apiKey, projectName, and environment to assemble the URL for indexConfigurationParameters.

But when init'ing, that projectName key is stripped away:

await pinecone.init({
    environment: process.env.PINECONE_ENVIRONMENT,
    apiKey: process.env.PINECONE_API_KEY,
    projectName: 'Project Name Here'
})

👆🏼 This will not working. I'm going to use http requests directly until this is fixed.

P.S. The documentation says to call pinecone.index(process.env.PINECONE_INDEX) but it's worth nothing the i in index needs to be capitalized.

[rschwabco]

@ediardo , @NCKLS , @JoshuaPerk - what Node version are you using? This is most likely an issue with using a version of Node that doesn't support fetch natively.

[rschwabco]

I've added an engines version specification to ensure this issue doesn't resurface:

  "engines": {
    "node": ">=18.0.0"
  },

[drob]

I'm running v16.19 in prod and unfortunately can't upgrade, so this would force me to fork or switch to a different library.

Would strongly prefer an approach like the one in rileytomasek/pinecone-client, i.e. allow older versions of node via a fetch polyfill. If you wanted to make it extra user friendly, you could detect the absence of native fetch and warn about it.

[rschwabco]

@drob as you suggested this PR add the cross-fetch polyfill.

[junhyeokkwak]

Seems like this issue was resolved at 0.0.10 but was then reintroduced in 0.0.11?

[Thushan96]

i use Node.js v18.15.0 , i also get the same error

[markwwd]

I use Node 16.17.1 and get the same error..

"Error: PineconeClient: Project name not set. Call init() first."

anyone?

[rschwabco]

@markwwd @junhyeokkwak @Thushan96 - Can you please provides steps for a repro?

[markwwd]

@rschwabco I solved it by using the latest NodeJS version. Though, it's giving a warning that it's an experimental feature and it might get replaced in the future (the fetch method).

[joschan21]

Having the same issue.
"PineconeClient: Error getting project name: ReferenceError: fetch is not defined"

[stephenkalnoske-sans]

Also had this issue. Reverting back to version 0.0.10 fixed it for me.