#ezarowny_error
1 messages · Page 1 of 1 (latest)
👋 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/1291819545379602452
📝 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.
- ezarowny_stripejs-webpack-blocking, 1 hour ago, 102 messages
Hi there
In case another data point helps, I'm able to load the card element on the second page in your payment flow (after typing in an amount, name, and email, and clicking "Enter Payment Info")
Did you happen to try what my teammate suggested re: using the /pure pattern? https://github.com/stripe/stripe-js?tab=readme-ov-file#importing-loadstripe-without-side-effects
And just to be clear, do you see the same "Stripe.js not available" error in the console log after clicking "Enter Payment Info"?
Pretty much right when the page loads
I don’t even need to proceed through checkout at all
No need to enter information
I think we load stripe pretty much immediately, although we don’t do anything with it like Mount elements until you’re in the second part of the flow
So I also see the "Stripe.js not available" error when I land on the page with name, amount, email address but that's not preventing me from navigating to the second page in the flow or seeing the card input fields 🤔
The input fields are facsimiles at first
You should see the little image of a credit card in the number field if stripe is active
Being able to type in there is another sign that it’s working
Because it’s just a div otherwise
I do see the card image and am able to type
Huh!
I am getting customers telling me that checkout isn’t working and they’re all using Firefox and experiencing that error
Yeah, even for me it’s intermittent
It’s more likely to happen if I do a hard reload with the cache busted
Back to another suggestion: were you able to try what my teammate suggested re: using the /pure pattern? https://github.com/stripe/stripe-js?tab=readme-ov-file#importing-loadstripe-without-side-effects
Hmm
We do already have stripe loaded on the page via the standard script tag
What will happen in that case if I use the pure import?
Stripe.js won't load until you explicitly call loadStripe
But the script tag is already there up in the head on most pages
For fraud fighting reasons
But I think I see what you're saying
Ah, I see
Well, maybe Stripe is still in the process of loading for some reason?
Not sure
I can always try it and see what happens in staging
It's so weird that this is Firefox only
Yeah, definitely odd.
Pure mode works in development
I'll try in staging and prod
Deploy takes a bit. Deploying to App Engine Flexible is ... slow
Seemed to work in dev (with the very neat stripe-cli)
Do you know if pure mode will still use a script tag if one exists?
I assume it just doesn't add the tag at import time.
I don't want to read any more JavaScript today than I have to 😆
Okay I actually read the code and pure mode has no promise
The only place we remove Stripe is on landing pages because, surprisingly, it has an non-negligible impact on Core Web Vitals
Looks good in staging but I'm getting some additional help validating and if that's good I'll push to prod
Sounds good!