can't anyone help with it?

show us some of the relevant code and logs

Well, it's about the Vercel bug:

Code:

router.get('/pinterest', async (req, res) => {
  const pinterest = data.map(({ pinner }) => ({
      pinner: {
          name: pinner.full_name
      }
  })) res.status(200).json(pinterest);
});

I got error on one request like can't read the property of undefined reading full_name

So, I changed the code like pinner?.full_name
Like this:

router.get('/pinterest', async (req, res) => {
  const pinterest = data.map(({ pinner }) => ({
      pinner: {
          name: pinner?.full_name
      }
  })) res.status(200).json(pinterest);
});

But my app stop working all of a sudden

what do you see in your vercel logs?

Are you doing checks to see if the correct result is being returned in your api?

Also where exactly is data coming from?

If you are using an external api make sure to check you're not getting rate limited or something

I run the same code on heroku, replit, render it works fine

But not for Vercel

Like why coz I just use pinner?.full_name Instead of pinner.full_name

It's coming from scraping

I checked everything it's just Vercel bug

Hmmm

Now, I changed my code to

pinner ? pinner.full_name : ''

It works without error

We can't use optional chaining (?.) In Vercel

I'm even using node 18x

admins should do something about this bug

Are you even using next.js or is this a home-built function on Vercel?

vercel.json:

{
  "version": 2,
  "builds": [
    {
      "src": "index.js",
      "use": "@now/node"
    }
  ],
  "routes": [
    {
      "src": "/(.*)",
      "dest": "index.js"
    }
  ]
}

Can't find support email

click "Create a case" button, fill out the form

also, since you are using the legacy builds instead of functions it is probably defaulting to an ancient version of Node.js (certainly without optional chaining)

Wait what?

WELL

Glad you got it!