Skip to content

Issues: node-formidable/formidable

the v3 plan?
#635 opened May 27, 2020 by tunnckoCore
Open 42
Support serverless environments
#594 opened Mar 27, 2020 by tunnckoCore
Open 8
Notes on/for v3 / v4
#830 opened Apr 1, 2022 by tunnckoCore
Open 20
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

Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort

Issues list

Refactor: Consider removing usage of setTimeout Area: files Things related to handling files, names, etc. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#894 opened Oct 9, 2022 by GrosSacASac
Include typings for Typescript, for V2/V3 of Formidable Priority: Medium This issue may be useful, and needs some attention. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. Status: In Progress This issue is being worked on, and has someone assigned. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#774 opened Nov 2, 2021 by gboer
Formidable detects MIME-type according to the file extension and not by the real content Area: files Things related to handling files, names, etc. Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Accepted It's clear what the subject of the issue is about, and what the resolution should be. Status: In Progress This issue is being worked on, and has someone assigned. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#749 opened Jul 10, 2021 by pubmikeb
Support serverless environments Area: APIs Things related to external and internal APIs Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Proposal A feature request or another suggestion. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#594 opened Mar 27, 2020 by tunnckoCore
How to halt formidable.parse Area: APIs Things related to external and internal APIs Priority: Low This issue can probably be picked up by anyone looking to contribute to the project. Status: Available No one has claimed for resolving this issue. Generally applied to bugs and enhancement issues. Type: Discussions Things that need discussion. Brainstorming. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#457 opened Jan 5, 2018 by arnabsarkardhn
Issue when parsing large files Area: streams Things related to handling streams, and bugs around them. Priority: Medium This issue may be useful, and needs some attention. Status: Available No one has claimed for resolving this issue. Generally applied to bugs and enhancement issues. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#449 opened Oct 27, 2017 by maximedupre
Support parsing of multipart/byteranges Area: APIs Things related to external and internal APIs Priority: Low This issue can probably be picked up by anyone looking to contribute to the project. Status: Available No one has claimed for resolving this issue. Generally applied to bugs and enhancement issues. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#390 opened Aug 20, 2016 by jcready
Add pause/resume handling to part passed to onPart. Area: streams Things related to handling streams, and bugs around them. Priority: High After critical issues are fixed, these should be dealt with before any further issues. Status: Awaiting Response Waiting author or someone to respond to question or clarification Status: Blocked Another issue needs to be resolved first or an external blocker. Type: Enhancement Most issues will probably be for additions or changes. Expected that this will result in a PR.
#388 opened Aug 9, 2016 by uformia Loading…
ProTip! Follow long discussions with comments:>50.