aith_api

[limpid shoal]

👋 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/1389712362436690041

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

[lilac ibex]

Hi there

[vital kestrel]

Hi

So yeah.. that's pretty much it. If I can add any further clarifications or explain the situation please let me know

[lilac ibex]

Just so we're on the same page, are you using Stripe's Node.js library as well? If so, which version are you using?

[vital kestrel]

Yes:

"stripe": "^18.2.1",

[lilac ibex]

Do you have a screenshot of this error? I'm not exactly sure what's triggering this since even the latest Node.js library is pinned to API version 2025-05-28.basil

[vital kestrel]

This is from my railway container. But I haven't changed the stripe version and this project builds locally just fine

These are more detailed

[lilac ibex]

Ah no, looks like I was wrong. Version 18.3.0 of Stripe's Node.js library uses API version 2025-06-30.basil

[lilac ibex]

I haven't used Railway before. Is it overriding the version of the Node.js library?

[vital kestrel]

That's just the thing.. if I change it to 2025-06-30.basil in my local, I cannot compile it since lib.d.ts has the 05-28 one. And it's the same ^18.2.1 being deployed

No

[lilac ibex]

Give me a few minutes to keep digging

[vital kestrel]

Okay a little update @lilac ibex

I fixed the version to 18.2.1 and it worked

Removed the caret

But this makes no sense 😅

Feels like a hacky solution haha

[boreal marlin]

yeah that seems weird

if you put it back does it still error?

Like this should never pull in 19.* from my (limited) understanding of Node.js versioning system

personally I do recommend always pinning to the exact version you test, I love semantic versioning and I push for it a lot, but I have seen us make a "small patch" release that broke something unexpected (and I have seen many SDKs/libs/companies do that mistake over the uears) so I don't trust the caret option in production

[vital kestrel]

No it's not pulling 19

[boreal marlin]

I wonder if you had a weird caching issue and you didn't have the composer.json you expected? And when you forced/pinned the 18.2.1 it kind of overwrote it?

[vital kestrel]

It pulls to 18.3.0 but yeah same thing

I've fixed the version to 18.2.1 now, removed the caret

[vital kestrel]

Lesson learned now haha

[vital kestrel]

The 18.2.1 was defined in my lock file as well so it should not be doing that

But it's a possibility for sure. Nothing else makes sense to me cause it should not be overwriting like that

[boreal marlin]

yeah not sure either