build(deps): bump axios from 0.27.2 to 1.3.4

[dependabot]

Bumps axios from 0.27.2 to 1.3.4.

Release notes

Sourced from axios's releases.

Release v1.3.4

Release notes:

Bug Fixes

• blob: added a check to make sure the Blob class is available in the browser's global scope; (#5548) (3772c8f)
• http: fixed regression bug when handling synchronous errors inside the adapter; (#5564) (a3b246c)

Contributors to this release

• Dmitriy Mozgovoy
• lcysgsg
• Michael Di Prisco

Release v1.3.3

Release notes:

Bug Fixes

• formdata: added a check to make sure the FormData class is available in the browser's global scope; (#5545) (a6dfa72)
• formdata: fixed setting NaN as Content-Length for form payload in some cases; (#5535) (c19f7bf)
• headers: fixed the filtering logic of the clear method; (#5542) (ea87ebf)

Contributors to this release

• Dmitriy Mozgovoy
• 陈若枫

Release v1.3.2

Release notes:

Bug Fixes

• http: treat http://localhost as base URL for relative paths to avoid ERR_INVALID_URL error; (#5528) (128d56f)
• http: use explicit import instead of TextEncoder global; (#5530) (6b3c305)

Contributors to this release

• Dmitriy Mozgovoy

Release v1.3.1

Release notes:

Bug Fixes

• formdata: add hotfix to use the asynchronous API to compute the content-length header value; (#5521) (96d336f)
• serializer: fixed serialization of array-like objects; (#5518) (08104c0)

Contributors to this release

• Dmitriy Mozgovoy

Release v1.3.0

Release notes:

... (truncated)

Changelog

Sourced from axios's changelog.

1.3.4 (2023-02-22)

Bug Fixes

• blob: added a check to make sure the Blob class is available in the browser's global scope; (#5548) (3772c8f)
• http: fixed regression bug when handling synchronous errors inside the adapter; (#5564) (a3b246c)

Contributors to this release

• Dmitriy Mozgovoy
• lcysgsg
• Michael Di Prisco

1.3.3 (2023-02-13)

Bug Fixes

• formdata: added a check to make sure the FormData class is available in the browser's global scope; (#5545) (a6dfa72)
• formdata: fixed setting NaN as Content-Length for form payload in some cases; (#5535) (c19f7bf)
• headers: fixed the filtering logic of the clear method; (#5542) (ea87ebf)

Contributors to this release

• Dmitriy Mozgovoy
• 陈若枫

1.3.2 (2023-02-03)

Bug Fixes

• http: treat http://localhost as base URL for relative paths to avoid ERR_INVALID_URL error; (#5528) (128d56f)
• http: use explicit import instead of TextEncoder global; (#5530) (6b3c305)

Contributors to this release

• Dmitriy Mozgovoy

1.3.1 (2023-02-01)

Bug Fixes

• formdata: add hotfix to use the asynchronous API to compute the content-length header value; (#5521) (96d336f)
• serializer: fixed serialization of array-like objects; (#5518) (08104c0)

Contributors to this release

... (truncated)

Commits

• 2e70cec chore(release): v1.3.4 (#5565)
• cbe2de6 chore(ci): remove team-reviewers config; (#5566)
• 2b1fc73 chore(docs): added missing config.transport doc (#5444)
• 3772c8f fix(blob): added a check to make sure the Blob class is available in the brow...
• a3b246c fix(http): fixed regression bug when handling synchronous errors inside the a...
• d9ebf8f chore(release): v1.3.3 (#5546)
• a43bca0 chore(example): fix source map urls; (#5467)
• a6dfa72 fix(formdata): added a check to make sure the FormData class is available in ...
• c19f7bf fix(formdata): fixed setting NaN as Content-Length for form payload in some c...
• ea87ebf fix(headers): fixed the filtering logic of the clear method; (#5542)
• 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)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
dgiot-doc	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 23, 2023 at 1:32AM (UTC)

[pull-request-quantifier-deprecated]

This PR has 2 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.json : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.