-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Please upgrade to latest, formidable@v3! Check these notes: https://bit.ly/2ZEqIau #1781
Comments
formidable v3 is ESM-only and can only be loaded async. but that is about to change. One plan is to switch to using fetch (undici) later on in next major release which is going to require NodeJS v16.8+ (b/c of undici requirement) then we will likely not need formidable anymore cuz we could just do: |
any update about this issue? |
Hey @jimmywarting , Hope all's good! Just wanted to touch base on the progress of this ticket about removing Formidable from Superagent. We know it's a priority due to the impending Formidable v2 deprecation and those pesky security issues. While we're in the process of fully ditching Formidable, how about we temporarily upgrade Superagent Formidable to version 3 (v3)?
I'd love to hear your thoughts on this idea. Oh, and here's the link to the Formidable Deprecation Notice for reference. Thanks a bunch for your attention to this! |
Yea, that would be a sensible thing to do. Quick to upgrade. Same functionality. one thing that formidable has that |
If you have plans for a major release, it would be great if the deprecated function |
It's possible that upgrading would also fix this bug: #1786 |
From version |
🚀 v9.0.0 released to npm 🚀 https://github.com/ladjs/superagent/releases/tag/v9.0.0 ref: #1800 Forward Email |
superagent/package.json
Line 27 in 83e92cb
The text was updated successfully, but these errors were encountered: