Outdated example documentation for CartProvider stripe prop
See original GitHub issueEDIT see the first reply on this issue
As per the image, on SSR, there is a non-serializable value in the state.
If I understand it correctly, it is redux-persist
that is the root of this message, but that’s a bit weird, since it seems to me that you have properly configured to ignore these messages here
To my knowledge, I am not using this lib in any unconventional way;
As per the error message, it’s the stripe
prop, which is a promise, that is the offender. However, it seems to me that I am initiating the CartProvider
very much the same way as in the example
Also, please not this only happens during SSR.
Thanks,
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Issues · dayhaysoos/use-shopping-cart
Shopping cart state and logic for Stripe. ... New examples welcome here! ... Outdated example documentation for CartProvider stripe prop.
Read more >CartProvider
To operate a checkout page without any server component you need to enable client-only checkout mode and insert your product information in your...
Read more >Allow order types to have no carts
The cart provider would not provide carts of that type (this might ... to move towards what used to be the old add...
Read more >Installation Guide for Custom Pricing
Set up Bold Memberships · Connect your Stripe Account to Bold ... var currentScript = document. ... Example: {% include 'bold-cart' %}.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@GGAlanSmithee
I didn’t know that this didn’t show up for the production build, thanks for that!
Maybe my goal really should be just to hide the error. Not sure if Next has anything for that but I’m going to look into it
@GGAlanSmithee thank you for your feedback! I have a big workshop I’m presenting this week, once that’s over with I can focus on addressing the issues you’ve raised. I really appreciate you!