-
Notifications
You must be signed in to change notification settings - Fork 60
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
ESM #429
Comments
Greetings @jimmywarting! At this stage, we still have a high number of customers running on Node.js 10.x. We've made the decision to hang onto Node 10.x support for a while longer, most likely until the deprecation of Node.js 12.x. When our dependencies move to an ESM-only model, as you call out, it puts unfortunate pressure on us to introduce a breaking change to our users. We read from the changelog that the 2.x line of node-fetch would continue to receive critical bug fixes and security patches. Is that still true? |
Yep, we understand that everyone can't update to esm right now so they will be stuck with cjs for a while longer. |
Excellent 😄 |
ref: #445 |
@JustinBeckwith Node.js versions up until version 19 are now deprecated (see here). Furthermore, upgrading node-fetch to at least version 3.2.10 would solve a memory leak issue (see here) and a Regular Expression Denial of Service issue (as can be seen here). Is there a chance that an ESM-only version of googleapis/gaxios will be published? This way, those running an outdated version of Node.js (13.2 and above) that does not support ESM import instructions should still be able to use CommonJS's dynamic import while making use of the latest fixes introduced by node-fetch. |
After upgrading to node 21, I now get: |
I just received this error after installing googleapis as well. Strange that it has not been fixed yet... |
Upgrading to |
This 2 are outdated...
gaxios/package.json
Lines 91 to 92 in a64f344
You are getting attacked by not one person (Sindre) that is converting all of his 1000+ packages to ESM-only
but now you also have two libraries that pushes for ESM only. node-fetch@3 (one of the most popular http library for NodeJS) went ESM-only too.
Where do you stand in this regards?
We (node-fetch) suggested to others who can't make the switch ESM to do the dynamic import('node-fetch') from commonjs while still using the latest version
The text was updated successfully, but these errors were encountered: