Warn if `formData` hash values are not strings, to prevent `source.on is not a function`
See original GitHub issueIn request/request#1495, the example code gets an error like source.on is not a function
because one of the values in the formData
has for a request
or request-promise
options hash is not a string.
The form-data
module should detect this error and tell the user to ensure all formdata
hash values are strings, or writeStreams
, or whatever else is valid.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:1
- Comments:12 (7 by maintainers)
Top Results From Across the Web
TypeError: source.on is not a function · Issue #2366 - GitHub
I'm trying to POST an array of values to a HTTP endpoint, and this is the error I receive: TypeError: source.on is not...
Read more >How can I solve source.on is not a function when using form ...
When I call the code from postman, I find this error "message": "source.on is not a function". I add return to see the...
Read more >Invoke-WebRequest (Microsoft.PowerShell.Utility)
When creating the $Form HashTable, the key names are used as form field names. By default, the values of the HashTable are converted...
Read more >jQuery.ajax() | jQuery API Documentation
A set of key/value pairs that configure the Ajax request. All settings are optional. A default can be set for any option with...
Read more >Changelog - Cypress Documentation
The .invoke() command now throws an error if the invoked function returns a ... Fixed an issue where cy.origin() would not prevent users...
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
You said, you’re no longer interested in this issue. So it was logical to close it. Please let me know if/when you want to get back to it. Thank you.
Thanks @alexindigo!