renovate[bot]
commented
1 year ago ⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving: await-remote-run@1.9.0
npm ERR! Found: @typescript-eslint/parser@5.62.0
npm ERR! node_modules/@typescript-eslint/parser
npm ERR! dev @typescript-eslint/parser@"^5.62.0" from the root project
npm ERR! peer @typescript-eslint/parser@"^5.0.0 || ^6.0.0" from eslint-config-airbnb-typescript@17.1.0
npm ERR! node_modules/eslint-config-airbnb-typescript
npm ERR! dev eslint-config-airbnb-typescript@"^17.1.0" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer @typescript-eslint/parser@"^6.0.0 || ^6.0.0-alpha" from @typescript-eslint/eslint-plugin@6.5.0
npm ERR! node_modules/@typescript-eslint/eslint-plugin
npm ERR! peer @typescript-eslint/eslint-plugin@"^5.13.0 || ^6.0.0" from eslint-config-airbnb-typescript@17.1.0
npm ERR! node_modules/eslint-config-airbnb-typescript
npm ERR! dev eslint-config-airbnb-typescript@"^17.1.0" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR!
npm ERR! For a full report see:
npm ERR! /tmp/worker/23c475/99bffe/cache/others/npm/_logs/2023-09-04T03_44_57_415Z-eresolve-report.txt
npm ERR! A complete log of this run can be found in: /tmp/worker/23c475/99bffe/cache/others/npm/_logs/2023-09-04T03_44_57_415Z-debug-0.log
codecov-commenter
This PR contains the following updates:
^18.16.18->^18.17.14^5.60.1->^5.62.0^0.32.2->^0.34.3^0.18.10->^0.19.2^8.43.0->^8.48.0^17.0.0->^17.1.0^2.27.5->^2.28.1^5.1.6->^5.2.2^0.32.2->^0.34.3Release Notes
typescript-eslint/typescript-eslint (@typescript-eslint/parser)
### [`v5.62.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5620-2023-07-10) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.61.0...v5.62.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. ### [`v5.61.0`](https://togithub.com/typescript-eslint/typescript-eslint/blob/HEAD/packages/parser/CHANGELOG.md#5610-2023-07-03) [Compare Source](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.1...v5.61.0) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website. #### [5.60.1](https://togithub.com/typescript-eslint/typescript-eslint/compare/v5.60.0...v5.60.1) (2023-06-26) **Note:** Version bump only for package [@typescript-eslint/parser](https://togithub.com/typescript-eslint/parser) You can read about our [versioning strategy](https://main--typescript-eslint.netlify.app/users/versioning) and [releases](https://main--typescript-eslint.netlify.app/users/releases) on our website.vitest-dev/vitest (@vitest/coverage-istanbul)
### [`v0.34.3`](https://togithub.com/vitest-dev/vitest/releases/tag/v0.34.3) [Compare Source](https://togithub.com/vitest-dev/vitest/compare/v0.34.2...v0.34.3) ##### 🚀 Features - **coverage**: Add `allowExternal` option - by [@vojvodics](https://togithub.com/vojvodics) and [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3894](https://togithub.com/vitest-dev/vitest/issues/3894) [(c03fa)](https://togithub.com/vitest-dev/vitest/commit/c03faa22) - **vitest**: Export all reporters in `vitest/reporters` - by [@Dunqing](https://togithub.com/Dunqing) and [@sheremet-va](https://togithub.com/sheremet-va) in [https://github.com/vitest-dev/vitest/issues/3980](https://togithub.com/vitest-dev/vitest/issues/3980) [(5704b)](https://togithub.com/vitest-dev/vitest/commit/5704b341) ##### 🐞 Bug Fixes - Should remove mockPath from callstack whether success or failed - by [@miserylee](https://togithub.com/miserylee) and **lijifei** in [https://github.com/vitest-dev/vitest/issues/3971](https://togithub.com/vitest-dev/vitest/issues/3971) [(5eb85)](https://togithub.com/vitest-dev/vitest/commit/5eb8561c) - Add workspace config files to default coverage excludes - by [@FelixGraf](https://togithub.com/FelixGraf) and [@AriPerkkio](https://togithub.com/AriPerkkio) in [https://github.com/vitest-dev/vitest/issues/3973](https://togithub.com/vitest-dev/vitest/issues/3973) [(20263)](https://togithub.com/vitest-dev/vitest/commit/20263d9d) - Report file error as aevanw/esbuild (esbuild)
### [`v0.19.2`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0192) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.1...v0.19.2) - Update how CSS nesting is parsed again CSS nesting syntax has been changed again, and esbuild has been updated to match. Type selectors may now be used with CSS nesting: ```css .foo { div { color: red; } } ``` Previously this was disallowed in the CSS specification because it's ambiguous whether an identifier is a declaration or a nested rule starting with a type selector without requiring unbounded lookahead in the parser. It has now been allowed because the CSS working group has decided that requiring unbounded lookahead is acceptable after all. Note that this change means esbuild no longer considers any existing browser to support CSS nesting since none of the existing browsers support this new syntax. CSS nesting will now always be transformed when targeting a browser. This situation will change in the future as browsers add support for this new syntax. - Fix a scope-related bug with `--drop-labels=` ([#3311](https://togithub.com/evanw/esbuild/issues/3311)) The recently-released `--drop-labels=` feature previously had a bug where esbuild's internal scope stack wasn't being restored properly when a statement with a label was dropped. This could manifest as a tree-shaking issue, although it's possible that this could have also been causing other subtle problems too. The bug has been fixed in this release. - Make renamed CSS names unique across entry points ([#3295](https://togithub.com/evanw/esbuild/issues/3295)) Previously esbuild's generated names for local names in CSS were only unique within a given entry point (or across all entry points when code splitting was enabled). That meant that building multiple entry points with esbuild could result in local names being renamed to the same identifier even when those entry points were built simultaneously within a single esbuild API call. This problem was especially likely to happen with minification enabled. With this release, esbuild will now avoid renaming local names from two separate entry points to the same name if those entry points were built with a single esbuild API call, even when code splitting is disabled. - Fix CSS ordering bug with `@layer` before `@import` CSS lets you put `@layer` rules before `@import` rules to define the order of layers in a stylesheet. Previously esbuild's CSS bundler incorrectly ordered these after the imported files because before the introduction of cascade layers to CSS, imported files could be bundled by removing the `@import` rules and then joining files together in the right order. But with `@layer`, CSS files may now need to be split apart into multiple pieces in the bundle. For example: /* Original code */ @layer start; @import "data:text/css,@layer inner.start;"; @import "data:text/css,@layer inner.end;"; @layer end; /* Old output (with --bundle) */ @layer inner.start; @layer inner.end; @layer start; @layer end; /* New output (with --bundle) */ @layer start; @layer inner.start; @layer inner.end; @layer end; - Unwrap nested duplicate `@media` rules ([#3226](https://togithub.com/evanw/esbuild/issues/3226)) With this release, esbuild's CSS minifier will now automatically unwrap duplicate nested `@media` rules: ```css /* Original code */ @media (min-width: 1024px) { .foo { color: red } @media (min-width: 1024px) { .bar { color: blue } } } /* Old output (with --minify) */ @media (min-width: 1024px){.foo{color:red}@media (min-width: 1024px){.bar{color:#00f}}} /* New output (with --minify) */ @media (min-width: 1024px){.foo{color:red}.bar{color:#00f}} ``` These rules are unlikely to be authored manually but may result from using frameworks such as Tailwind to generate CSS. ### [`v0.19.1`](https://togithub.com/evanw/esbuild/blob/HEAD/CHANGELOG.md#0191) [Compare Source](https://togithub.com/evanw/esbuild/compare/v0.19.0...v0.19.1) - Fix a regression with `baseURL` in `tsconfig.json` ([#3307](https://togithub.com/evanw/esbuild/issues/3307)) The previous release moved `tsconfig.json` path resolution before `--packages=external` checks to allow the [`paths` field](https://www.typescriptlang.org/tsconfig#paths) in `tsconfig.json` to avoid a package being marked as external. However, that reordering accidentally broke the behavior of the `baseURL` field from `tsconfig.json`. This release moves these path resolution rules around again in an attempt to allow both of these cases to work. - Parse TypeScript type arguments for JavaScript decorators ([#3308](https://togithub.com/evanw/esbuild/issues/3308)) When parsing JavaScript decorators in TypeScript (i.e. with `experimentalDecorators` disabled), esbuild previously didn't parse type arguments. Type arguments will now be parsed starting with this release. For example: ```ts @fooConfiguration
📅 Schedule: Branch creation - "before 4am on the first day of the month" in timezone Pacific/Auckland, 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.
This PR has been generated by Mend Renovate. View repository job log here.