-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to node 20 #653
Comments
That would be great, but I wouldn't hold my breath. Development on this extension has been inactive for some time now. |
Yes, I have gathered as much. Very unfortunate. We have decided as a team to rebuilt the functionality in house now :/ Thanks for the heads up! |
Solution is to change this line to "node": "20"
|
Are there any known forks of this project that are keeping things up to date? |
When the extension was handed over to invertase, the following comment was made, quote:
Looks like that was a very weak commitment, to say the least.
So question to @paulasjes-stripe is: is stripe aware of the lack of maintenance, and is there any plan for improvement, or should we move to something different? |
I might also add that dont forget to change the runtime aswell when changing the package.json version. |
Node 18 is going to be deprecated and decommissioned by GCP.
Are there any plans to upgrade the version for the extension?
The text was updated successfully, but these errors were encountered: