⬆️ Update devDependencies #21

renovate · 2023-08-01T04:20:13Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@trivago/prettier-plugin-sort-imports	`4.1.1` -> `4.2.0`
@types/node (source)	`20.3.2` -> `20.4.5`
@typescript-eslint/eslint-plugin	`5.60.1` -> `5.62.0`
@typescript-eslint/parser	`5.60.1` -> `5.62.0`
@vitest/coverage-c8 (source)	`0.32.2` -> `0.33.0`
esbuild	`0.18.10` -> `0.18.17`
eslint (source)	`8.43.0` -> `8.46.0`
typescript (source)	`5.1.5` -> `5.1.6`
vite (source)	`4.3.9` -> `4.4.7`
vitest	`0.32.2` -> `0.33.0`

Release Notes

trivago/prettier-plugin-sort-imports (@trivago/prettier-plugin-sort-imports)

`v4.2.0`

Compare Source

Chore

update prettier peer dependency semVer to include 3.x #239 by basselworkforce

typescript-eslint/typescript-eslint (@typescript-eslint/eslint-plugin)

`v5.62.0`

Compare Source

Bug Fixes

eslint-plugin: [comma-spacing] allow no space after trailing comma in objects and arrays (#6938) (24bdacc)
eslint-plugin: [prefer-includes] escape special characters (#7161) (5a347a5), closes #7145
eslint-plugin: replace auto-fix of class literal property style rule with suggestion (#7054) (a8c824a)

Features

eslint-plugin: [prefer-nullish-coalescing] add ignorePrimitives option (#6487) (6edaa04)

You can read about our versioning strategy and releases on our website.

`v5.61.0`

Compare Source

Features

eslint-plugin: [ban-types] ban types in extends and implements (#7129) (997783f)
use graphemer instead of grapheme-splitter (#7069) (faea3ff)

You can read about our versioning strategy and releases on our website.

5.60.1 (2023-06-26)

Note: Version bump only for package @typescript-eslint/eslint-plugin

You can read about our versioning strategy and releases on our website.

typescript-eslint/typescript-eslint (@typescript-eslint/parser)

`v5.62.0`

Compare Source

Note: Version bump only for package @typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

`v5.61.0`

Compare Source

Note: Version bump only for package @typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

5.60.1 (2023-06-26)

Note: Version bump only for package @typescript-eslint/parser

You can read about our versioning strategy and releases on our website.

vitest-dev/vitest (@vitest/coverage-c8)

`v0.33.0`

Compare Source

🚨 Breaking Changes

Revert default include patterns - by @so1ve #3729
- 0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.

🐞 Bug Fixes

Add missing JSDom living keys - by @DerZade in https://github.com/vitest-dev/vitest/issues/3702 (83a86)
vite-node:
- Don't fail when importing Promise module - by @sheremet-va (08192)
- Allow importing node:test - by @sheremet-va (db22c)

View changes on GitHub

`v0.32.4`

Compare Source

🐞 Bug Fixes

browser: Correctly optimize CJS dependencies - by @sheremet-va (3d090)

View changes on GitHub

View changes on GitHub

evanw/esbuild (esbuild)

`v0.18.17`

Compare Source

Support An+B syntax and :nth-*() pseudo-classes in CSS

This adds support for the :nth-child(), :nth-last-child(), :nth-of-type(), and :nth-last-of-type() pseudo-classes to esbuild, which has the following consequences:
- The An+B syntax is now parsed, so parse errors are now reported
- An+B values inside these pseudo-classes are now pretty-printed (e.g. a leading + will be stripped because it's not in the AST)
- When minification is enabled, An+B values are reduced to equivalent but shorter forms (e.g. 2n+0 => 2n, 2n+1 => odd)
- Local CSS names in an of clause are now detected (e.g. in :nth-child(2n of :local(.foo)) the name foo is now renamed)
```
/* Original code */
.foo:nth-child(+2n+1 of :local(.bar)) {
  color: red;
}

/* Old output (with --loader=local-css) */
.stdin_foo:nth-child(+2n + 1 of :local(.bar)) {
  color: red;
}

/* New output (with --loader=local-css) */
.stdin_foo:nth-child(2n+1 of .stdin_bar) {
  color: red;
}
```
Adjust CSS nesting parser for IE7 hacks (#3272)

This fixes a regression with esbuild's treatment of IE7 hacks in CSS. CSS nesting allows selectors to be used where declarations are expected. There's an IE7 hack where prefixing a declaration with a * causes that declaration to only be applied in IE7 due to a bug in IE7's CSS parser. However, it's valid for nested CSS selectors to start with *. So esbuild was incorrectly parsing these declarations and anything following it up until the next { as a selector for a nested CSS rule. This release changes esbuild's parser to terminate the parsing of selectors for nested CSS rules when a ; is encountered to fix this edge case:
```
/* Original code */
.item {
  *width: 100%;
  height: 1px;
}

/* Old output */
.item {
  *width: 100%; height: 1px; {
  }
}

/* New output */
.item {
  *width: 100%;
  height: 1px;
}
```
Note that the syntax for CSS nesting is about to change again, so esbuild's CSS parser may still not be completely accurate with how browsers do and/or will interpret CSS nesting syntax. Expect additional updates to esbuild's CSS parser in the future to deal with upcoming CSS specification changes.
Adjust esbuild's warning about undefined imports for TypeScript import equals declarations (#3271)

In JavaScript, accessing a missing property on an import namespace object is supposed to result in a value of undefined at run-time instead of an error at compile-time. This is something that esbuild warns you about by default because doing this can indicate a bug with your code. For example:
```
// app.js
import * as styles from './styles'
console.log(styles.buton)
```
```
// styles.js
export let button = {}
```
If you bundle app.js with esbuild you will get this:
```
▲ [WARNING] Import "buton" will always be undefined because there is no matching export in "styles.js" [import-is-undefined]

    app.js:2:19:
      2 │ console.log(styles.buton)
        │                    ~~~~~
        ╵                    button

  Did you mean to import "button" instead?

    styles.js:1:11:
      1 │ export let button = {}
        ╵            ~~~~~~
```
However, there is TypeScript-only syntax for import equals declarations that can represent either a type import (which esbuild should ignore) or a value import (which esbuild should respect). Since esbuild doesn't have a type system, it tries to only respect import equals declarations that are actually used as values. Previously esbuild always generated this warning for unused imports referenced within import equals declarations even when the reference could be a type instead of a value. Starting with this release, esbuild will now only warn in this case if the import is actually used. Here is an example of some code that no longer causes an incorrect warning:
```
// app.ts
import * as styles from './styles'
import ButtonType = styles.Button
```
```
// styles.ts
export interface Button {}
```

`v0.18.16`

Compare Source

Fix a regression with whitespace inside :is() (#3265)

The change to parse the contents of :is() in version 0.18.14 introduced a regression that incorrectly flagged the contents as a syntax error if the contents started with a whitespace token (for example div:is( .foo ) {}). This regression has been fixed.

`v0.18.15`

Compare Source

Add the --serve-fallback= option (#2904)

The web server built into esbuild serves the latest in-memory results of the configured build. If the requested path doesn't match any in-memory build result, esbuild also provides the --servedir= option to tell esbuild to serve the requested path from that directory instead. And if the requested path doesn't match either of those things, esbuild will either automatically generate a directory listing (for directories) or return a 404 error.

Starting with this release, that last step can now be replaced with telling esbuild to serve a specific HTML file using the --serve-fallback= option. This can be used to provide a "not found" page for missing URLs. It can also be used to implement a single-page app that mutates the current URL and therefore requires the single app entry point to be served when the page is loaded regardless of whatever the current URL is.
Use the tsconfig field in package.json during extends resolution (#3247)

This release adds a feature from TypeScript 3.2 where if a tsconfig.json file specifies a package name in the extends field and that package's package.json file has a tsconfig field, the contents of that field are used in the search for the base tsconfig.json file.
Implement CSS nesting without :is() when possible (#1945)

Previously esbuild would always produce a warning when transforming nested CSS for a browser that doesn't support the :is() pseudo-class. This was because the nesting transform needs to generate an :is() in some complex cases which means the transformed CSS would then not work in that browser. However, the CSS nesting transform can often be done without generating an :is(). So with this release, esbuild will no longer warn when targeting browsers that don't support :is() in the cases where an :is() isn't needed to represent the nested CSS.

In addition, esbuild's nested CSS transform has been updated to avoid generating an :is() in cases where an :is() is preferable but there's a longer alternative that is also equivalent. This update means esbuild can now generate a combinatorial explosion of CSS for complex CSS nesting syntax when targeting browsers that don't support :is(). This combinatorial explosion is necessary to accurately represent the original semantics. For example:
```
/* Original code */
.first,
.second,
.third {
  & > & {
    color: red;
  }
}

/* Old output (with --target=chrome80) */
:is(.first, .second, .third) > :is(.first, .second, .third) {
  color: red;
}

/* New output (with --target=chrome80) */
.first > .first,
.first > .second,
.first > .third,
.second > .first,
.second > .second,
.second > .third,
.third > .first,
.third > .second,
.third > .third {
  color: red;
}
```
This change means you can now use CSS nesting with esbuild when targeting an older browser that doesn't support :is(). You'll now only get a warning from esbuild if you use complex CSS nesting syntax that esbuild can't represent in that older browser without using :is(). There are two such cases:
```
/* Case 1 */
a b {
  .foo & {
    color: red;
  }
}

/* Case 2 */
a {
  > b& {
    color: red;
  }
}
```
These two cases still need to use :is(), both for different reasons, and cannot be used when targeting an older browser that doesn't support :is():
```
/* Case 1 */
.foo :is(a b) {
  color: red;
}

/* Case 2 */
a > a:is(b) {
  color: red;
}
```

Automatically lower inset in CSS for older browsers

With this release, esbuild will now automatically expand the inset property to the top, right, bottom, and left properties when esbuild's target is set to a browser that doesn't support inset:

/* Original code */
.app {
  position: absolute;
  inset: 10px 20px;
}

/* Old output (with --target=chrome80) */
.app {
  position: absolute;
  inset: 10px 20px;
}

/* New output (with --target=chrome80) */
.app {
  position: absolute;
  top: 10px;
  right: 20px;
  bottom: 10px;
  left: 20px;
}

Add support for the new @starting-style CSS rule (#3249)

This at rule allow authors to start CSS transitions on first style update. That is, you can now make the transition take effect when the display property changes from none to block.
```
/* Original code */
@&#8203;starting-style {
  h1 {
    background-color: transparent;
  }
}

/* Output */
@&#8203;starting-style{h1{background-color:transparent}}
```
This was contributed by @yisibl.

`v0.18.14`

Compare Source

Implement local CSS names (#20)

This release introduces two new loaders called global-css and local-css and two new pseudo-class selectors :local() and :global(). This is a partial implementation of the popular CSS modules approach for avoiding unintentional name collisions in CSS. I'm not calling this feature "CSS modules" because although some people in the community call it that, other people in the community have started using "CSS modules" to refer to something completely different and now CSS modules is an overloaded term.

Here's how this new local CSS name feature works with esbuild:
- Identifiers that look like .className and #idName are global with the global-css loader and local with the local-css loader. Global identifiers are the same across all files (the way CSS normally works) but local identifiers are different between different files. If two separate CSS files use the same local identifier .button, esbuild will automatically rename one of them so that they don't collide. This is analogous to how esbuild automatically renames JS local variables with the same name in separate JS files to avoid name collisions.
- It only makes sense to use local CSS names with esbuild when you are also using esbuild's bundler to bundle JS files that import CSS files. When you do that, esbuild will generate one export for each local name in the CSS file. The JS code can import these names and use them when constructing HTML DOM. For example:
```
// app.js
import { outerShell } from './app.css'
const div = document.createElement('div')
div.className = outerShell
document.body.appendChild(div)
```
```
/* app.css */
.outerShell {
  position: absolute;
  inset: 0;
}
```
  When you bundle this with esbuild app.js --bundle --loader:.css=local-css --outdir=out you'll now get this (notice how the local CSS name outerShell has been renamed):
```
// out/app.js
(() => {
  // app.css
  var outerShell = "app_outerShell";

  // app.js
  var div = document.createElement("div");
  div.className = outerShell;
  document.body.appendChild(div);
})();
```
```
/* out/app.css */
.app_outerShell {
  position: absolute;
  inset: 0;
}
```
  This feature only makes sense to use when bundling is enabled both because your code needs to import the renamed local names so that it can use them, and because esbuild needs to be able to process all CSS files containing local names in a single bundling operation so that it can successfully rename conflicting local names to avoid collisions.
- If you are in a global CSS file (with the global-css loader) you can create a local name using :local(), and if you are in a local CSS file (with the local-css loader) you can create a global name with :global(). So the choice of the global-css loader vs. the local-css loader just sets the default behavior for identifiers, but you can override it on a case-by-case basis as necessary. For example:
```
:local(.button) {
  color: red;
}
:global(.button) {
  color: blue;
}
```
  Processing this CSS file with esbuild with either the global-css or local-css loader will result in something like this:
```
.stdin_button {
  color: red;
}
.button {
  color: blue;
}
```
- The names that esbuild generates for local CSS names are an implementation detail and are not intended to be hard-coded anywhere. The only way you should be referencing the local CSS names in your JS or HTML is with an import statement in JS that is bundled with esbuild, as demonstrated above. For example, when --minify is enabled esbuild will use a different name generation algorithm which generates names that are as short as possible (analogous to how esbuild minifies local identifiers in JS).
- You can easily use both global CSS files and local CSS files simultaneously if you give them different file extensions. For example, you could pass --loader:.css=global-css and --loader:.module.css=local-css to esbuild so that .css files still use global names by default but .module.css files use local names by default.
- Keep in mind that the css loader is different than the global-css loader. The :local and :global annotations are not enabled with the css loader and will be passed through unchanged. This allows you to have the option of using esbuild to process CSS containing while preserving these annotations. It also means that local CSS names are disabled by default for now (since the css loader is currently the default for CSS files). The :local and :global syntax may be enabled by default in a future release.
Note that esbuild's implementation does not currently have feature parity with other implementations of modular CSS in similar tools. This is only a preliminary release with a partial implementation that includes some basic behavior to get the process started. Additional behavior may be added in future releases. In particular, this release does not implement:
- The composes pragma
- Tree shaking for unused local CSS
- Local names for keyframe animations, grid lines, @container, @counter-style, etc.
Issue #20 (the issue for this feature) is esbuild's most-upvoted issue! While this release still leaves that issue open, it's an important first step in that direction.
Parse :is, :has, :not, and :where in CSS

With this release, esbuild will now parse the contents of these pseudo-class selectors as a selector list. This means you will now get syntax warnings within these selectors for invalid selector syntax. It also means that esbuild's CSS nesting transform behaves slightly differently than before because esbuild is now operating on an AST instead of a token stream. For example:
```
/* Original code */
div {
  :where(.foo&) {
    color: red;
  }
}

/* Old output (with --target=chrome90) */
:where(.foo:is(div)) {
  color: red;
}

/* New output (with --target=chrome90) */
:where(div.foo) {
  color: red;
}
```

`v0.18.13`

Compare Source

Add the --drop-labels= option (#2398)

If you want to conditionally disable some development-only code and have it not be present in the final production bundle, right now the most straightforward way of doing this is to use the --define: flag along with a specially-named global variable. For example, consider the following code:
```
function main() {
  DEV && doAnExpensiveCheck()
}
```
You can build this for development and production like this:
- Development: esbuild --define:DEV=true
- Production: esbuild --define:DEV=false
One drawback of this approach is that the resulting code crashes if you don't provide a value for DEV with --define:. In practice this isn't that big of a problem, and there are also various ways to work around this.

However, another approach that avoids this drawback is to use JavaScript label statements instead. That's what the --drop-labels= flag implements. For example, consider the following code:
```
function main() {
  DEV: doAnExpensiveCheck()
}
```
With this release, you can now build this for development and production like this:
- Development: esbuild
- Production: esbuild --drop-labels=DEV
This means that code containing optional development-only checks can now be written such that it's safe to run without any additional configuration. The --drop-labels= flag takes comma-separated list of multiple label names to drop.
Avoid causing unhandledRejection during shutdown (#3219)

All pending esbuild JavaScript API calls are supposed to fail if esbuild's underlying child process is unexpectedly terminated. This can happen if SIGINT is sent to the parent node process with Ctrl+C, for example. Previously doing this could also cause an unhandled promise rejection when esbuild attempted to communicate this failure to its own child process that no longer exists. This release now swallows this communication failure, which should prevent this internal unhandled promise rejection. This change means that you can now use esbuild's JavaScript API with a custom SIGINT handler that extends the lifetime of the node process without esbuild's internals causing an early exit due to an unhandled promise rejection.
Update browser compatibility table scripts

The scripts that esbuild uses to compile its internal browser compatibility table have been overhauled. Briefly:
- Converted from JavaScript to TypeScript
- Fixed some bugs that resulted in small changes to the table
- Added caniuse-lite and @mdn/browser-compat-data as new data sources (replacing manually-copied information)
This change means it's now much easier to keep esbuild's internal compatibility tables up to date. You can review the table changes here if you need to debug something about this change:
- JS table changes
- CSS table changes

`v0.18.12`

Compare Source

Fix a panic with const enum inside parentheses (#3205)

This release fixes an edge case where esbuild could potentially panic if a TypeScript const enum statement was used inside of a parenthesized expression and was followed by certain other scope-related statements. Here's a minimal example that triggers this edge case:
```
(() => {
  const enum E { a };
  () => E.a
})
```
Allow a newline in the middle of TypeScript export type statement (#3225)

Previously esbuild incorrectly rejected the following valid TypeScript code:
```
export type
{ T };

export type
* as foo from 'bar';
```
Code that uses a newline after export type is now allowed starting with this release.
Fix cross-module inlining of string enums (#3210)

A refactoring typo in version 0.18.9 accidentally introduced a regression with cross-module inlining of string enums when combined with computed property accesses. This regression has been fixed.
Rewrite .js to .ts inside packages with exports (#3201)

Packages with the exports field are supposed to disable node's path resolution behavior that allows you to import a file with a different extension than the one in the source code (for example, importing foo/bar to get foo/bar.js). And TypeScript has behavior where you can import a non-existent .js file and you will get the .ts file instead. Previously the presence of the exports field caused esbuild to disable all extension manipulation stuff which included both node's implicit file extension searching and TypeScript's file extension swapping. However, TypeScript appears to always apply file extension swapping even in this case. So with this release, esbuild will now rewrite .js to .ts even inside packages with exports.
Fix a redirect edge case in esbuild's development server (#3208)

The development server canonicalizes directory URLs by adding a trailing slash. For example, visiting /about redirects to /about/ if /about/index.html would be served. However, if the requested path begins with two slashes, then the redirect incorrectly turned into a protocol-relative URL. For example, visiting //about redirected to //about/ which the browser turns into http://about/. This release fixes the bug by canonicalizing the URL path when doing this redirect.

`v0.18.11`

Compare Source

Fix a TypeScript code generation edge case (#3199)

This release fixes a regression in version 0.18.4 where using a TypeScript namespace that exports a class declaration combined with --keep-names and a --target of es2021 or earlier could cause esbuild to export the class from the namespace using an incorrect name (notice the assignment to X2._Y vs. X2.Y):

// Original code

// Old output (with --keep-names --target=es2021)
var X;
((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2._Y = _Y;
})(X || (X = {}));

// New output (with --keep-names --target=es2021)
var X;
((X2) => {
  const _Y = class _Y {
  };
  __name(_Y, "Y");
  let Y = _Y;
  X2.Y = _Y;
})(X || (X = {}));

eslint/eslint (eslint)

`v8.46.0`

Compare Source

Features

8a93438 feat: require-unicode-regexp support v flag (#17402) (SUZUKI Sosuke)
1a2f966 feat: no-useless-escape support v flag (#17420) (Yosuke Ota)
ee68d1d feat: no-empty-character-class support v flag (#17419) (Milos Djermanovic)
853d32b feat: deprecate no-return-await (#17417) (Carlos Lopez)
d4f02e4 feat: no-control-regex support v flag (#17405) (Yosuke Ota)
2a35f3e feat: prefer-named-capture-group support v flag (#17409) (Yosuke Ota)
8ca8b50 feat: Better error message for flat config plugins (#17399) (Nicholas C. Zakas)
509f753 feat: no-misleading-character-class support v flag (#17406) (Yosuke Ota)
3caf514 feat: no-regex-spaces support v flag (#17407) (Yosuke Ota)
b7fad2b feat: prefer-regex-literals support v flag (#17410) (Yosuke Ota)
a6a3ad4 feat: no-useless-backreference support v flag (#17408) (Yosuke Ota)
94954a7 feat: no-invalid-regexp support v flag (#17404) (Yosuke Ota)
1af6eac feat: adds option for allowing empty object patterns as parameter (#17365) (Tanuj Kanti)
cf03104 feat: Improve config error messages (#17385) (Nicholas C. Zakas)

Bug Fixes

9803c7c fix: FlatESLint#getRulesMetaForResults shouldn't throw on unknown rules (#17393) (Milos Djermanovic)
42faa17 fix: Update no-loop-func to not overlap with no-undef (#17358) (Matt Wilkinson)

Documentation

4d474e3 docs: update with TypeScript info (#17423) (James)
091f44e docs: File extension named processor deprecation (#17362) (Matt Wilkinson)
9254a6c docs: Update README (GitHub Actions Bot)
6d6dc51 docs: fix overlapping of open in playground button (#17403) (Tanuj Kanti)
7fc3a2c docs: Add private class features info to no-underscore-dangle (#17386) (Matt Wilkinson)
da73e58 docs: Migrating eslint-env configuration comments (#17390) (Francesco Trotta)
80dffed docs: fix Ignoring Files section in config migration guide (#17392) (Milos Djermanovic)
8a9abb7 docs: Update README (GitHub Actions Bot)
7e9be4b docs: Update README (GitHub Actions Bot)
0b0bbe0 docs: Update README (GitHub Actions Bot)

Chores

d1eb7e4 chore: Update ecosystem dependencies (#17427) (Nicholas C. Zakas)
fab9e97 chore: package.json update for eslint-config-eslint release (ESLint Jenkins)
6246711 chore: package.json update for @eslint/js release (ESLint Jenkins)
0aa0bc3 chore: Add PRs to triage project (#17421) (Nicholas C. Zakas)

`v8.45.0`

Compare Source

Features

cdd063c feat: Expose LegacyESLint in unsupported API (#17341) (Nicholas C. Zakas)
d34abe5 feat: fix indent rule for else-if (#17318) (Milos Djermanovic)

Bug Fixes

b79b6fb fix: Fix suggestion message in no-useless-escape (#17339) (Francesco Trotta)
c667055 fix: provide unique fix and fix.range objects in lint messages (#17332) (Milos Djermanovic)

Documentation

89f3225 docs: add playground links to correct and incorrect code blocks (#17306) (Josh Goldberg ✨)
f8892b5 docs: Expand rule option schema docs (#17198) (Matt Wilkinson)
8bcbf11 docs: Config Migration Guide (#17230) (Ben Perlmutter)
bb30908 docs: Update README (GitHub Actions Bot)
84d243b docs: Update README (GitHub Actions Bot)
b762632 docs: Update README (GitHub Actions Bot)
138c096 docs: add more prefer-destructuring examples with array destructuring (#17330) (Milos Djermanovic)
1fc50a8 docs: max-len rule code and tabWidth as positional arguments (#17331) (Jesús Leganés-Combarro)

Chores

68f63d7 chore: package.json update for @eslint/js release (ESLint Jenkins)
5ca9b4d chore: update eslint-config-eslint exports (#17336) (Milos Djermanovic)
7bf2e86 chore: remove unused dependencies (#17352) (Percy Ma)
c6f8cd0 chore: Remove defaultIgnores from FlatESLint private members (#17349) (Francesco Trotta)
0052374 chore: move jsdoc settings to eslint-config-eslint (#17338) (唯然)

[`v8.44.0`](https://tog

Configuration

📅 Schedule: Branch creation - "on the first day of the month" in timezone GMT, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

⬆️ Update devDependencies

9f3badc

renovate bot merged commit a0e3b89 into main Aug 1, 2023
1 check passed

renovate bot deleted the renovate/devdependencies branch August 1, 2023 06:03

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

⬆️ Update devDependencies #21

⬆️ Update devDependencies #21

renovate bot commented Aug 1, 2023

⬆️ Update devDependencies #21

⬆️ Update devDependencies #21

Conversation

renovate bot commented Aug 1, 2023

Release Notes

Chore

Bug Fixes

Features

Features

5.60.1 (2023-06-26)

5.60.1 (2023-06-26)

🚨 Breaking Changes

🐞 Bug Fixes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

Features

Bug Fixes

Documentation

Chores

Features

Bug Fixes

Documentation

Chores

[v8.44.0](https://tog

Configuration

[`v8.44.0`](https://tog