Skip to content

issues Search Results · repo:node-formidable/formidable language:JavaScript

Filter by

557 results
 (69 ms)

557 results

innode-formidable/formidable (press backspace or delete to remove)

node-formidable/formidable
Typo: in package.json

108: ulpoad , should be 108: upload ,
  • Coding4ever123
  • Opened 
    2 days ago
  • #1015

node-formidable/formidable
Dependabot: Formidable relies on hexoid to prevent guessing of filenames for untrusted executable content

We have received following dependabot on 01/May/2025: Formidable relies on hexoid to prevent guessing of filenames for untrusted executable content Formidable (aka node-formidable) 2.1.0 through 3.x before ...
  • kishorchouhan
  • 1
  • Opened 
    9 days ago
  • #1014

node-formidable/formidable
Attaching 'data' listeners immediately

!-- ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ You must complete this entire issue template to receive support. You MUST NOT remove, change, or replace the template with your own format. A missing or incomplete report will cause ...
bug
  • mxschmitt
  • 5
  • Opened 
    19 days ago
  • #1011

node-formidable/formidable
NPM packages marked as deprecated breaks semver constraints

There are various later versions of Formidable v2 which are marked as deprecated on the NPM package registry, of which I can fully see the reason why, however this unfortunately breaks semver constraints ...
  • AlexC
  • 4
  • Opened 
    on Apr 29
  • #1008

node-formidable/formidable
trimmed v3 benchmarks

Used @mjackson s benchmarks suite, seems like Formidable v3 is performing pretty well, especially in large files. link https://github.com/mjackson/remix-the-web/pull/66 where we can find the trimmed down ...
  • tunnckoCore
  • 3
  • Opened 
    on Apr 25
  • #996

node-formidable/formidable
2.1.3 is not compatible with node@16, but 2.1.2 is ok

Two days ago, the formidable upgrade to 2.1.3, but it is not compatible with node@16, it s required greater than v18. The 2.1.2 is ok. with 2.1.3 and nodejs@16.14.0 ERR TypeError: os.machine is not a ...
  • TaylorPzreal
  • 12
  • Opened 
    on Apr 21
  • #994

node-formidable/formidable
RFC: Add option to treat small text/plain files as "fields"

As discussed here #875 It s a weird thing but.. behind an option it could be an interesting feature.
  • tunnckoCore
  • Opened 
    on Apr 18
  • #991

node-formidable/formidable
Parsing array fields

!-- ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ You must complete this entire issue template to receive support. You MUST NOT remove, change, or replace the template with your own format. A missing or incomplete report will cause ...
  • hernanrz
  • 2
  • Opened 
    on Mar 14
  • #988

node-formidable/formidable
File handle not released after options.maxFiles check

!-- ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ You must complete this entire issue template to receive support. You MUST NOT remove, change, or replace the template with your own format. A missing or incomplete report will cause ...
Area: files
bug
  • si-yingjie
  • Opened 
    on Mar 14
  • #987

node-formidable/formidable
Trying to use this in AWS Lambda but looks like it requires request object

Hi. I was trying to use this in an AWS Lambda that is behind an API Gateway. I am seeing an error because it looks like formidable is trying to read the content-length header from the request object. Is ...
  • micronaut
  • 3
  • Opened 
    on Feb 13
  • #986
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue origami icon

Learn how you can use GitHub Issues to plan and track your work.

Save views for sprints, backlogs, teams, or releases. Rank, sort, and filter issues to suit the occasion. The possibilities are endless.Learn more about GitHub Issues
ProTip! 
Restrict your search to the title by using the in:title qualifier.
Issue search results · GitHub