chore(deps): update dependency formidable to v2 - abandoned

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
formidable	^1.2.1 -> ^2.0.0
@types/formidable (source)	1.0.31 -> 2.0.5

---

Release Notes

node-formidable/formidable

v2.1.1

Compare Source

v2.1.0

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

• feat: files are detected if a mimetype is present (previously it was based on filename)
• feat: add options.filter (#​716)
• feat: add code and httpCode to most errors (#​686)
• rename: option.hash into option.hashAlgorithm (#​689)
• rename: file.path into file.filepath (#​689)
• rename: file.type into file.mimetype (#​689)
• refactor: split file.name into file.newFilename and file.originalFilename (#​689)
• feat: prevent directory traversal attacks by default (#​689)
• meta: stop including test files in npm (7003c)
• fix: handle invalid filenames (d0a34)
• feat: add fileWriteStreamHandler option
• feat: add allowEmptyFiles and minFileSize options
• feat: Array support for fields and files (#​380, #​340, #​367, #​33, #​498, #​280, #​483)
• possible partial fix of #​386 with #​380 (need tests and better implementation)
• refactor: use hasOwnProperty in check against files/fields (#​522)
• meta: do not promote IncomingForm and add exports.default (#​529)
• meta: Improve examples and tests (#​523)
• refactor: First step of Code quality improvements (#​525)
• chore(funding): remove patreon & add npm funding field (#​525
• feat: use Modern Streams API (#​531)
• fix: urlencoded parsing to emit end #​543, introduced in #​531
• fix(tests): include multipart and qs parser unit tests, part of #​415
• fix: reorganize exports + move parsers to src/parsers/
• fix: update docs and examples #​544 (#​248, #​335, #​371, #​372, #​387, partly #​471, #​535)
• feat: introduce Plugins API, fix silent failing tests (#​545, #​391, #​407, #​386, #​374, #​521, #​267)
• fix: exposing file writable stream errors (#​520, #​316, #​469, #​470)
• feat: custom file (re)naming, thru options.filename (#​591, #​84, #​86, #​94, #​154, #​158, #​488, #​595)

v1.2.6

Compare Source

v1.2.5

Compare Source

v1.2.4

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/marked
npm ERR!   marked@"^0.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer marked@"^0.4.0 || ^0.5.0" from [email protected]
npm ERR! node_modules/marked-terminal
npm ERR!   marked-terminal@"^3.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/marked
npm ERR!   peer marked@"^0.4.0 || ^0.5.0" from [email protected]
npm ERR!   node_modules/marked-terminal
npm ERR!     marked-terminal@"^3.1.1" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-05-16T03_30_29_314Z-debug-0.log

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.

[renovate]

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.