Closed lsegal closed 3 years ago
3.
v2 (soon haha) and then shortly after v3. Users should use v3 in my opinion
4.
Only v3 is being developed, v2 is ready for release and did not have changes made in the last couple of months, the reason I started v3 is to separate it from v2 since it does have a couple of breaking changes
Continue here https://github.com/node-formidable/formidable/issues/412, I can give you access if you want
@lsegal
So, v2 as the next latest
dist-tag for some time, and v3 as v3
or canary
or dev
dist-tag, then we'll move v3 to latest
and mark v2 as deprecated in npm.
_Apologies for breaking the ISSUETEMPLATE here, but I'm not sure it applies, since this is more of a question than a feature request / bug report.
It's been a while since any updates have been made on the v2 or v3 roadmaps, and it seems like formidable is still released on npm as 1.2.2, which formidable's own README on npmjs lists as "deprecated". According to #412, none of the maintainers have current access to npm in order to publish updates(??), and there seem to be 2 different major versions under active development (#718 and #635), with oddly v2 being the later discussion(?).
Based on the above I have a few related questions as we try to determine if we should be using this library, or an alternative:
Thanks in advance!