richnologies / ngx-stripe

Angular 6+ wrapper for StripeJS
MIT License
219 stars 77 forks source link

Support for Angular v15 #187

Closed justvamp closed 1 year ago

justvamp commented 1 year ago

Angular 15 is released, it would be great to support it. Thanks!

richnologies commented 1 year ago

Hi @justvamp,

I'm working on the new version. It might take a few more days because I want to fully support Standalone Components and to deprecate some internal artefacts that should never been exposed.

Thanks for your patience

R

justvamp commented 1 year ago

Sounds amazing! Thank you for the fastest reply, patiently waiting :)

Dzivo commented 1 year ago

@richnologies that is nice. for now just use --force on npm install if you are not going to production it does work for me

ahmadallw commented 1 year ago

hi @justvamp, Any new good news about the new version?

Thank you!

justvamp commented 1 year ago

hi @justvamp, Any new good news about the new version?

Thank you!

Hi, I guess this question is for @richnologies

ArthurBardakov commented 1 year ago

@richnologies Hi! Any progress on the support of Angular 15? It would be great to have an update on that!

richnologies commented 1 year ago

Hi everyone!

Sorry about the delay. We have been working on both fronts, adding new features from Stripe and working with the Standalone API from Angular in case we need to introduce any breaking changes.

So, two new versions shipped today:

The version for Angular v15 does not include yet support for Standalone components because we are still doing some test, but we can release this version now because we are certain now we won't introduce any breaking changes.

Again, sorry for any inconvenience

Let me know if you have any issues with the new version

Kind Regards

R

s2young commented 1 year ago

If it helps, I am using standalone components. I'm trying to access StripeFactoryService on my component and it's not there. Is there any way to provide it or instantiate it manually?

richnologies commented 1 year ago

Hey @s2young, happy to discuss this issue with you. Do you mind to create a separate issue?