#alxtzheptabasecom_api

1 messages ¡ Page 1 of 1 (latest)

hollow tendonBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1277978119021789228

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.

primal condor
#

Without touching the upgrade option on the dashboard yet (as it requires more attention). I've tried upgrading the node lib to v16.8.0, configuring new Stripe(0x00, { apiVersion: '2024-06-20' }), or setting API version in the func call.

(example)

await stripe.customers.search(
  {
    query: 0x00
  },
  {
    apiVersion: '2024-06-20',
  }
);
#

However, with all these attempts. The server-side stripe object seems to always be initialised with VERSION: '8.209.0'. With stripe.customers.search() missing

sonic valley
#

You must not be upgrading stripe-node properly

#

It seems like you're still get the old 8.x version of the package

primal condor
#

Really, interesting. Let me check again

sonic valley
#

How are you triggering the update?

#

Honestly, you might just try manually deleting the stripe-node directory from node_modules

primal condor
#

Yup, I'm definitely killing the entire node_modules to being with.

Also you're correct. Somehow the stripe class I'm importing is on a legacy version in the first place. Looks like my fault more

sonic valley
#

Weird, but yea this is definitely just loading the wrong version for some reason

#

Are you using any global cache that needs to be wiped?

#

Is your package.json referring to the correct/explicit new version?