Bump ts-jest from 26.5.2 to 26.5.3

[dependabot]

Bumps ts-jest from 26.5.2 to 26.5.3.

Changelog

Sourced from ts-jest's changelog.

26.5.3 (2021-03-03)

Bug Fixes

• config: create fallback jest config when jest config is undefined (#2421) (0fb6b45), closes #2085
• remove @types/jest from direct dep (#2416) (060302e), closes #2406 #2411
• compiler: return original file content on emit skip (#2408) (cfba8f4), closes #2407

27.0.0-next.7 (2021-02-24)

Bug Fixes

• compiler: exclude files in outDir from compiler source files (#2375) (ec68c74), closes #2350 #2374
• config: cache config and compiler correctly between runs (#2356) (5f91336)
• config: improve emit skipped error message (#2358) (2ae8df4), closes #2350
• typings: set correct typing for tsconfig option (#2383) (584324a), closes #2368

Commits

• ee10b67 chore(release): 26.5.3
• 174fb74 refactor(config): expose root logger constant (#2422)
• 0fb6b45 fix(config): create fallback jest config when jest config is undefined (#2421)
• 060302e fix: remove @types/jest from direct dep (#2416)
• cfba8f4 fix(compiler): return original file content on emit skip (#2408)
• See full diff 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)

[pull-request-quantifier-deprecated]

Pull Request Quantified (Extra Small)

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

---

Quantification details

Label      : Extra Small
Size       : +4 -35
Percentile : 15.6%

Total files changed: 1

Change summary by file extension:
.lock : +4 -35

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 detetcted.
• 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.

[dependabot]

Superseded by #25.