fix(deps): update dependencies (non-major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
dotenv	^16.2.0 -> ^16.3.0
eslint (source)	^8.42.0 -> ^8.43.0

---

Release Notes

motdotla/dotenv

v16.3.0

Compare Source

Added

• Optionally pass DOTENV_KEY to options rather than relying on process.env.DOTENV_KEY. Defaults to process.env.DOTENV_KEY #​754

eslint/eslint

v8.43.0

Compare Source

Features

• 14581ff feat: directive prologue detection and autofix condition in quotes (#​17284) (Francesco Trotta)
• e50fac3 feat: add declaration loc to message in block-scoped-var (#​17252) (Milos Djermanovic)
• 1b7faf0 feat: add skipJSXText option to no-irregular-whitespace rule (#​17182) (Azat S)

Bug Fixes

• 5338b56 fix: normalize cwd passed to ESLint/FlatESLint constructor (#​17277) (Milos Djermanovic)
• 54383e6 fix: Remove no-extra-parens autofix for potential directives (#​17022) (Francesco Trotta)

Documentation

• 8b855ea docs: resubmit pr17061 doc changes (#​17292) (唯然)
• 372722e docs: resubmit pr17012 doc changes (#​17293) (唯然)
• 67e7af3 docs: resubmit custom-rules doc changes (#​17294) (唯然)
• 9e3d77c docs: Resubmit Fix formatting in Custom Rules docs (#​17281) (Milos Djermanovic)
• 503647a docs: Resubmit markVariableAsUsed docs (#​17280) (Nicholas C. Zakas)
• e0cf0d8 docs: Custom rule & plugin tutorial (#​17024) (Ben Perlmutter)
• 8e51ea9 docs: resubmit no-new rule documentation (#​17264) (Nitin Kumar)
• 1b217f8 docs: resubmit Custom Processors documentation (#​17265) (Nitin Kumar)
• 428fc76 docs: resubmit Create Plugins documentation (#​17268) (Nitin Kumar)
• bdca88c docs: resubmit Configuration Files documentation (#​17267) (Nitin Kumar)
• f5c01f2 docs: resubmit Manage Issues documentation (#​17266) (Nitin Kumar)
• b199295 docs: Resubmit custom rules update docs (#​17273) (Ben Perlmutter)
• 0e9980c docs: add new omitLastInOneLineClassBody option to the semi rule (#​17263) (Nitin Kumar)
• cb2560f docs: Resubmit getScope/getDeclaredVariables docs (#​17262) (Nicholas C. Zakas)
• 85d2b30 docs: explain how to include predefined globals (#​17261) (Marcus Wyatt)
• de4d3c1 docs: update flat config default ignore patterns (#​17258) (Milos Djermanovic)
• 3912f3a docs: Improve ignores documentation (#​17239) (Francesco Trotta)
• 35e11d3 docs: fix typos and missing info (#​17257) (Ed Lucas)
• 0bc257c docs: Clarify no-div-regex rule docs (#​17051) (#​17255) (Francesco Trotta)
• 788d836 docs: add references to MIT License (#​17248) (Milos Djermanovic)
• 58aab6b docs: Update README (GitHub Actions Bot)
• 3ef5814 docs: Revert all changes after the license change (#​17227) (Milos Djermanovic)
• 03fc4aa docs: Update README (GitHub Actions Bot)

Chores

• 78350f6 chore: upgrade @​eslint/js@​8.43.0 (#​17295) (Milos Djermanovic)
• 62bf759 chore: package.json update for @​eslint/js release (ESLint Jenkins)
• e0a2448 chore: docs package.license ISC => MIT (#​17254) (唯然)
• 6a0196c chore: use eslint-plugin-eslint-plugin flat configs (#​17204) (Milos Djermanovic)

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Shanghai, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

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

---

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

[codecov]

Codecov Report

Merging #984 (2205823) into main (545c054) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #984   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            8         8           
  Lines           57        57           
  Branches         2         2           
=========================================
  Hits            57        57           

[pull-request-quantifier-deprecated]

This PR has 8 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       : +4 -4
Percentile : 3.2%

Total files changed: 3

Change summary by file extension:
.json : +4 -4
.lock : +0 -0

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.