chore(deps): bump form-data-encoder from 1.7.2 to 2.0.1

[dependabot]

Bumps form-data-encoder from 1.7.2 to 2.0.1.

Release notes

Sourced from form-data-encoder's releases.

2.0.1

Update

• Adjust minimal required Node.js version to 14.17

---

All changes: octet-stream/form-data-encoder@v2.0.0...v2.0.1

2.0.0

Breaking

• Drop CommonJS support. The package is now ESM only;
• Remove Encoder from exports;
• Remove deprecated isFormDataLike helper. Use isFormData instead.

Update

• Minimal required Node.js version is 14.18;
• Headers in FormDataEncoder.headers property can be accessed in case-insensitive manner. TypeScript users still have correct TS typings, but only for original and lowercased keys (for example Content-Type and content-type);
• FormData instance will be preserved in array inside of FormDataEncoder instance (previously it held a reference to given FormData instance);
• Deprecate isFileLike helper. Use isFile instead;
• Deprecate FormDataEncoder.getContentLength() method. The content-length is now static value, so this method makes no sense. Use FormDataEncoder.contentLength or FormDataEncoder.headers["content-length"] instead.

Add

• Expose FormDataEncoderHeaders type.

---

All changes: octet-stream/form-data-encoder@v1.7.2...v2.0.0

Commits

• 87655b8 Bump version: 2.0.0 -> 2.0.1
• 7fee5a0 Adjust minimal Node.js version to 14.17
• 4975e93 Remove unnecessary type casting
• 9f477ef Remove unnecessary tsconfig for AVA
• f376d3a Re-enable postinstall script
• 48ff598 Bump version: 1.7.2 -> 2.0.0
• c265a11 Add a note about lookbehind in RegExp
• 212e7be Use named exports for consistency across the project.
• 139a6cc Deduplicate readonly props declarations in constructor
• b2e6a94 Fixes for documentation
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[char0n]

lquixada/cross-fetch#111

[char0n]

@octet-stream any suggestions how to incorporate this version into swagger-js without converting swagger-js to type=module?

[octet-stream]

Hi! Tanks for asking. There's nothing much changed between 1.7.2 and 2.0.1, so you can keep using 1.x until you convert your package to ESM. I will keep support for this, for sometime if that would be necessary and if npm gives me ability to do so.

[octet-stream]

Alternatively, you can import module using dynamic import syntax, if that is applicable.

[char0n]

Hi! Tanks for asking. There's nothing much changed between 1.7.2 and 2.0.1, so you can keep using 1.x until you convert your package to ESM. I will keep support for this, for sometime if that would be necessary and if npm gives me ability to do so.

All right, thanks, that's what I thought. There is not much we can do except to convert to ESM. We'll stick with 1.* release branch for some time, and then we'll see.

Alternatively, you can import module using dynamic import syntax, if that is applicable.

Unfortunately it does not. It would introduce synchronicity to synchronous code and part of the library would need to be rewritten.

Thanks for a quick answer!

[char0n]

Closing for now.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.