FormData is incompatible with current version of mailgun.js
See original GitHub issueHello,
I recently upgraded a project that made use of this library to typescript and I’ve been getting a typescript error.
. It seems the form-data library expects an optional parameter and that doesn't align with the type definition for the mailgun class. I tried using `global.FormData` instead of the npm library but that was incompatible with `mailgun.js`.I’m not sure if I’m doing something wrong but I’ll appreciate any help I can get. I also tried downgrading form-data
to v3 and I still got the same error.
"mailgun.js": "4.1.4"
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:6 (3 by maintainers)
Top Results From Across the Web
mailgun.js - npm
A javascript sdk for Mailgun built with webpack, babel & es6. This can be used in node or in the browser*.. Latest version:...
Read more >Mailgun.js: A JavaScript SDK for Mailgun - Morioh
Mailgun.js is a JavaScript sdk for Mailgun built with webpack, babel & es6. ... NOTE: starting from version 3.0 you need to pass...
Read more >Multipart/form-data field names are encoded incorrectly
I'm using Mailgun's REST API in a Cloudflare Worker. The API requires a POST of multipart/form-data. Some of the API's form fields have...
Read more >Third-party software dependencies | Elastic Cloud Enterprise ...
Library Version Optional/Required Packaged
akka‑actor_2.13 2.6.18 Required Yes
akka‑http‑core_2.13 10.2.7 Required Yes
akka‑http‑json4s_2.13 1.27.0 Required Yes
Read more >Messages — Mailgun API documentation
text version of the email. This field is always present. If the incoming message only has HTML body, Mailgun will create a text...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello @gdieguez Adding “allowSyntheticDefaultImports”: true option to your tsconfig.json file should fix this issue.
Okay, thank you for your time, I am glad that you don’t have the issue anymore.