#EmilyH-elements
1 messages · Page 1 of 1 (latest)
@prime pond when you say "stripe-elements" can you link me to the exact library/page/Github project you're referring to?
we are using this in package-lock of one of our projects "dependencies": { "react-stripe-elements": "^3.0.0" }, however a colleague recently mentioned when building a new project that that was deprecating so has used "@stripe/react-stripe-js": "^1.4.1", "@stripe/stripe-js": "^1.15.1", instead....
npm packages...
Should i convert our older project to use the newer...
ah ok you mean react-stripe-elements
yes sorry
thats is not being maintained yes , see the readme at https://github.com/stripe-archive/react-stripe-elements
is there a cut off point i will have to have made the change?
it's never going to stop working really, but it won't have any more releases or work done to it; for new projects you should use use react-stripe-js yes
not really no, the npm package is just a wrapper around our main library (https://js.stripe.com/v3) and that is not going anywhere
ok cool. i suppose though if other packages keep going up in versions, and we want something long term that will work continue to work with everything else and be improved, we should swap over
yep