Bump axios and start-server-and-test

[dependabot]

Bumps axios and start-server-and-test. These dependencies needed to be updated together.
Updates axios from 0.19.2 to 0.21.4

Release notes

Sourced from axios's releases.

v0.21.4

0.21.4 (September 6, 2021)

Fixes and Functionality:

• Fixing JSON transform when data is stringified. Providing backward compatibility and complying to the JSON RFC standard (#4020)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Guillaume Fortaine
• Yusuke Kawasaki
• Dmitriy Mozgovoy

v0.21.3

0.21.3 (September 4, 2021)

Fixes and Functionality:

• Fixing response interceptor not being called when request interceptor is attached (#4013)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Julian Hollmann

v0.21.2

0.21.2 (September 4, 2021)

Fixes and Functionality:

• Updating axios requests to be delayed by pre-emptive promise creation (#2702)
• Adding "synchronous" and "runWhen" options to interceptors api (#2702)
• Updating of transformResponse (#3377)
• Adding ability to omit User-Agent header (#3703)
• Adding multiple JSON improvements (#3688, #3763)
• Fixing quadratic runtime and extra memory usage when setting a maxContentLength (#3738)
• Adding parseInt to config.timeout (#3781)
• Adding custom return type support to interceptor (#3783)
• Adding security fix for ReDoS vulnerability (#3980)

Internal and Tests:

• Updating build dev dependancies (#3401)
• Fixing builds running on Travis CI (#3538)
• Updating follow rediect version (#3694, #3771)
• Updating karma sauce launcher to fix failing sauce tests (#3712, #3717)
• Updating content-type header for application/json to not contain charset field, according do RFC 8259 (#2154)
• Fixing tests by bumping karma-sauce-launcher version (#3813)
• Changing testing process from Travis CI to GitHub Actions (#3938)

Documentation:

• Updating documentation around the use of AUTH_TOKEN with multiple domain endpoints (#3539)

... (truncated)

Changelog

Sourced from axios's changelog.

0.21.4 (September 6, 2021)

Fixes and Functionality:

• Fixing JSON transform when data is stringified. Providing backward compatability and complying to the JSON RFC standard (#4020)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Jay
• Guillaume Fortaine
• Yusuke Kawasaki
• Dmitriy Mozgovoy

0.21.3 (September 4, 2021)

Fixes and Functionality:

• Fixing response interceptor not being called when request interceptor is attached (#4013)

Huge thanks to everyone who contributed to this release via code (authors listed below) or via reviews and triaging on GitHub:

• Jay
• Julian Hollmann

0.21.2 (September 4, 2021)

Fixes and Functionality:

• Updating axios requests to be delayed by pre-emptive promise creation (#2702)
• Adding "synchronous" and "runWhen" options to interceptors api (#2702)
• Updating of transformResponse (#3377)
• Adding ability to omit User-Agent header (#3703)
• Adding multiple JSON improvements (#3688, #3763)
• Fixing quadratic runtime and extra memory usage when setting a maxContentLength (#3738)
• Adding parseInt to config.timeout (#3781)
• Adding custom return type support to interceptor (#3783)
• Adding security fix for ReDoS vulnerability (#3980)

Internal and Tests:

• Updating build dev dependancies (#3401)
• Fixing builds running on Travis CI (#3538)
• Updating follow rediect version (#3694, #3771)
• Updating karma sauce launcher to fix failing sauce tests (#3712, #3717)
• Updating content-type header for application/json to not contain charset field, according do RFC 8259 (#2154)
• Fixing tests by bumping karma-sauce-launcher version (#3813)
• Changing testing process from Travis CI to GitHub Actions (#3938)

Documentation:

• Updating documentation around the use of AUTH_TOKEN with multiple domain endpoints (#3539)
• Remove duplication of item in changelog (#3523)

... (truncated)

Commits

• 66c4602 Merge branch 'master' into release/0.21.4
• fc15665 [Releasing] v0.21.4
• c2714f0 [Updating] incorrect JSON syntax in README.md
• 0fc7248 fix json transform when data is pre-stringified (#4020)
• 90205f8 Change headers type to string record (#3021)
• 92b29d2 Make the default type of response data never (#3002)
• 4eeb3b1 Improved type-safety for AxiosRequestConfig (#2995)
• cd7ff04 Adding HTTP status code to error.toJSON (#2956)
• b5a1a67 Adding nodejs http.request option: insecureHTTPParser (#2930)
• 4f25380 Exposing the Axios constructor in index.d.ts (#2872)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by jasonsaayman, a new releaser for axios since your current version.

Updates start-server-and-test from 1.11.3 to 1.14.0

Release notes

Sourced from start-server-and-test's releases.

v1.14.0

1.14.0 (2021-09-02)

v1.13.1

1.13.1 (2021-07-26)

Bug Fixes

• deps: update dependency wait-on to v6 (#307) (eeaaf92)

v1.13.0

1.13.0 (2021-07-22)

Features

• api: adds check for http status 304 (#311) (c0adf51)

v1.12.6

1.12.6 (2021-07-06)

Bug Fixes

• deps: update dependency debug to v4.3.2 (3b17fb0)

v1.12.5

1.12.5 (2021-06-06)

Bug Fixes

• deps: update dependency execa to v5.1.1 (b6b09bc)

v1.12.4

1.12.4 (2021-06-04)

Bug Fixes

• deps: update dependency execa to v5.1.0 (c546d00)

v1.12.3

1.12.3 (2021-05-24)

Bug Fixes

• arg parsing on windows, close #239 (#244) (d37318e)

... (truncated)

Commits

• 693dc2c FEAT: Allow interval option from environment variable (#315)
• 7ac144f explain the server not responding (#314)
• eeaaf92 fix(deps): update dependency wait-on to v6 (#307)
• c0adf51 feat(api): adds check for http status 304 (#311)
• 3b17fb0 fix(deps): update dependency debug to v4.3.2
• b6b09bc fix(deps): update dependency execa to v5.1.1
• c546d00 fix(deps): update dependency execa to v5.1.0
• 445fe2f add example with multiple test commands, closes #304
• d37318e fix: arg parsing on windows, close #239 (#244)
• a131819 fix(deps): update dependency execa to v5 (#290)
• 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[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: 2

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.