FloPay SDK Changelog

v1.2.5 - Simpler @flopay/js install with bundled Stripe runtime #

Installing @flopay/js no longer requires a separate @stripe/stripe-js install. The Stripe browser SDK is now a direct dependency, and a clearer error is surfaced if the Stripe runtime ever fails to load.

FloPay SDK v1.2.5 simplifies installation of @flopay/js by bundling @stripe/stripe-js as a direct dependency. Consumers no longer need to install or pin the Stripe browser SDK themselves, and a load-time failure of the Stripe runtime now produces a clearly labelled FloPay error instead of failing silently.

What changed

• @flopay/js now declares @stripe/stripe-js (^9.7.0) as a direct runtime dependency. The previous optional peer-dependency declaration has been removed, so package managers install the Stripe browser SDK automatically alongside @flopay/js.
• If the Stripe browser SDK ever fails to resolve at runtime, the SDK now throws a FloPayError with code: 'StripeJsLoadFailed' and a descriptive message, replacing the prior silent failure path.

Developer notes

• Update your package.json to @flopay/js@1.2.5 (matching @flopay/react@1.2.5, @flopay/node@1.2.5, and @flopay/shared@1.2.5) and reinstall.
• You can drop any direct @stripe/stripe-js entry from your application's dependencies if you only added it to satisfy the previous peer-dependency requirement. Applications that import @stripe/stripe-js directly for their own purposes can continue to pin it themselves.
• No public exports, props, or request/response shapes have changed.