chore(deps): update all non-major dependencies

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@apollo/server	^4.4.1 -> ^4.7.1
@graphql-codegen/plugin-helpers	^4.0.0 -> ^4.2.0
@graphql-codegen/typescript	^3.0.1 -> ^3.0.4
@graphql-codegen/typescript-resolvers	^3.1.0 -> ^3.2.1
@nuxt/devtools	^0.2.5 -> ^0.5.0
@nuxt/kit	^3.2.3 -> ^3.5.0
@​nuxt/module-builder	^0.2.1 -> ^0.3.1
@nuxt/schema	^3.2.3 -> ^3.5.0
@nuxt/test-utils	^3.2.3 -> ^3.5.0
@typescript-eslint/eslint-plugin	^5.54.0 -> ^5.59.6
@typescript-eslint/parser	^5.54.0 -> ^5.59.6
@vitest/coverage-c8 (source)	^0.29.2 -> ^0.31.1
eslint (source)	^8.35.0 -> ^8.40.0
eslint-config-prettier	^8.6.0 -> ^8.8.0
nuxt	^3.2.3 -> ^3.5.0
pnpm (source)	8.0.0 -> 8.5.1
prettier (source)	^2.8.4 -> ^2.8.8
vitest	^0.29.2 -> ^0.31.1

---

Release Notes

apollographql/apollo-server

v4.7.1

Compare Source

Patch Changes

• #​7539 5d3c45be9 Thanks @​mayakoneval! - 🐛 Bug Fix for Apollo Server Landing Pages on Safari. A Content Security Policy was added to our landing page html so that Safari can run the inline scripts we use to call the Embedded Sandbox & Explorer.

v4.7.0

Compare Source

Minor Changes

• #​7504 22a5be934 Thanks @​mayakoneval! - In the Apollo Server Landing Page Local config, you can now opt out of the telemetry that Apollo Studio runs in the
  embedded Sandbox & Explorer landing pages. This telemetry includes Google Analytics for event tracking and
  Sentry for error tracking.

  Example of the new config option:

  const server = new ApolloServer({
    typeDefs,
    resolvers,
    plugins: [
      process.env.NODE_ENV === 'production'
        ? ApolloServerPluginLandingPageProductionDefault({
            graphRef: 'my-graph-id@my-graph-variant',
            embed: {
              runTelemetry: false
            },
          })
        : ApolloServerPluginLandingPageLocalDefault({
            embed: {
              runTelemetry: false
            },
          }),
    ],
  });
  

v4.6.0

Compare Source

Minor Changes

• #​7465 1e808146a Thanks @​trevor-scheer! - Introduce new opt-in configuration option to mitigate v4 status code regression

  Apollo Server v4 accidentally started responding to requests with an invalid variables object with a 200 status code, where v3 previously responded with a 400. In order to not break current behavior (potentially breaking users who have creatively worked around this issue) and offer a mitigation, we've added the following configuration option which we recommend for all users.

  new ApolloServer({
    // ...
    status400ForVariableCoercionErrors: true,
  });

  Specifically, this regression affects cases where input variable coercion fails. Variables of an incorrect type (i.e. String instead of Int) or unexpectedly null are examples that fail variable coercion. Additionally, missing or incorrect fields on input objects as well as custom scalars that throw during validation will also fail variable coercion. For more specifics on variable coercion, see the "Input Coercion" sections in the GraphQL spec.

  This will become the default behavior in Apollo Server v5 and the configuration option will be ignored / no longer needed.

Patch Changes

• #​7454 f6e3ae021 Thanks @​trevor-scheer! - Start building packages with TS 5.x, which should have no effect for users

• #​7433 e0db95b96 Thanks @​KGAdamCook! - Previously, when users provided their own documentStore, Apollo Server used a random prefix per schema in order to guarantee there was no shared state from one schema to the next. Now Apollo Server uses a hash of the schema, which enables the provided document store to be shared if you choose to do so.

v4.5.0

Compare Source

Minor Changes

• #​7431 7cc163ac8 Thanks @​mayakoneval! - In the Apollo Server Landing Page Local config, you can now automatically turn off autopolling on your endpoints as well as pass headers used to introspect your schema, embed an operation from a collection, and configure whether the endpoint input box is editable. In the Apollo Server Landing Page Prod config, you can embed an operation from a collection & we fixed a bug introduced in release 4.4.0

  Example of all new config options:

  const server = new ApolloServer({
    typeDefs,
    resolvers,
    plugins: [
      process.env.NODE_ENV === 'production'
        ? ApolloServerPluginLandingPageProductionDefault({
            graphRef: 'my-graph-id@my-graph-variant',
            collectionId: 'abcdef',
            operationId: '12345'
            embed: true,
            footer: false,
          })
        : ApolloServerPluginLandingPageLocalDefault({
            collectionId: 'abcdef',
            operationId: '12345'
            embed: {
              initialState: {
                pollForSchemaUpdates: false,
                sharedHeaders: {
                  "HeaderNeededForIntrospection": "ValueForIntrospection"
                },
              },
              endpointIsEditable: true,
            },
            footer: false,
          }),
    ],
  });
  
  

• #​7430 b694bb1dd Thanks @​mayakoneval! - We now send your @​apollo/server version to the embedded Explorer & Sandbox used in the landing pages for analytics.

Patch Changes

• #​7432 8cbc61406 Thanks @​mayakoneval! - Bug fix: TL;DR revert a previous change that stops passing includeCookies from the prod landing page config.

  Who was affected?

  Any Apollo Server instance that passes a graphRef to a production landing page with a non-default includeCookies value that does not match the Include cookies setting on your registered variant on studio.apollographql.com.

  How were they affected?

  From release 4.4.0 to this patch release, folks affected would have seen their Explorer requests being sent with cookies included only if they had set Include cookies on their variant. Cookies would not have been included by default.

dotansimha/graphql-code-generator (@​graphql-codegen/plugin-helpers)

v4.2.0

Compare Source

Minor Changes

• #​9151 b7dacb21f Thanks @​'./user/schema.mappers#UserMapper',! - Add watchPattern config option for generates sections.

  By default, watch mode automatically watches all GraphQL schema and document files. This means when a change is detected, Codegen CLI is run.

  A user may want to run Codegen CLI when non-schema and non-document files are changed. Each generates section now has a watchPattern option to allow more file patterns to be added to the list of patterns to watch.

  In the example below, mappers are exported from schema.mappers.ts files. We want to re-run Codegen if the content of *.mappers.ts files change because they change the generated types file. To solve this, we can add mapper file patterns to watch using the glob pattern used for schema and document files.

  // codegen.ts
  const config: CodegenConfig = {
    schema: 'src/schema/**/*.graphql',
    generates: {
      'src/schema/types.ts': {
        plugins: ['typescript', 'typescript-resolvers'],
        config: {
          mappers: {
  
            Book: './book/schema.mappers#BookMapper',
          },
        }
        watchPattern: 'src/schema/**/*.mappers.ts', // Watches mapper files in `watch` mode. Use an array for multiple patterns e.g. `['src/*.pattern1.ts','src/*.pattern2.ts']`
      },
    },
  };

  Then, run Codegen CLI in watch mode:

  yarn graphql-codegen --watch

  Now, updating *.mappers.ts files re-runs Codegen! 🎉

  Note: watchPattern is only used in watch mode i.e. running CLI with --watch flag.

Patch Changes

• f104619ac Thanks @​saihaj! - Resolve issue with nesting fields in @provides directive being prevented

v4.1.0

Compare Source

Minor Changes

• #​8893 a118c307a Thanks @​n1ru4l! - mark plugins in config optional

• #​8723 a3309e63e Thanks @​kazekyo! - Introduce a new feature called DocumentTransform.

  DocumentTransform is a functionality that allows you to modify documents before they are processed by plugins. You can use functions passed to the documentTransforms option to make changes to GraphQL documents.

  To use this feature, you can write documentTransforms as follows:

  import type { CodegenConfig } from '@​graphql-codegen/cli';
  
  const config: CodegenConfig = {
    schema: 'https://localhost:4000/graphql',
    documents: ['src/**/*.tsx'],
    generates: {
      './src/gql/': {
        preset: 'client',
        documentTransforms: [
          {
            transform: ({ documents }) => {
              // Make some changes to the documents
              return documents;
            },
          },
        ],
      },
    },
  };
  export default config;

  For instance, to remove a @localOnlyDirective directive from documents, you can write the following code:

  import type { CodegenConfig } from '@​graphql-codegen/cli';
  import { visit } from 'graphql';
  
  const config: CodegenConfig = {
    schema: 'https://localhost:4000/graphql',
    documents: ['src/**/*.tsx'],
    generates: {
      './src/gql/': {
        preset: 'client',
        documentTransforms: [
          {
            transform: ({ documents }) => {
              return documents.map(documentFile => {
                documentFile.document = visit(documentFile.document, {
                  Directive: {
                    leave(node) {
                      if (node.name.value === 'localOnlyDirective') return null;
                    },
                  },
                });
                return documentFile;
              });
            },
          },
        ],
      },
    },
  };
  export default config;

  DocumentTransform can also be specified by file name. You can create a custom file for a specific transformation and pass it to documentTransforms.

  Let's create the document transform as a file:

  module.exports = {
    transform: ({ documents }) => {
      // Make some changes to the documents
      return documents;
    },
  };

  Then, you can specify the file name as follows:

  import type { CodegenConfig } from '@​graphql-codegen/cli';
  
  const config: CodegenConfig = {
    schema: 'https://localhost:4000/graphql',
    documents: ['src/**/*.tsx'],
    generates: {
      './src/gql/': {
        preset: 'client',
        documentTransforms: ['./my-document-transform.js'],
      },
    },
  };
  export default config;

Patch Changes

• #​8879 8206b268d Thanks @​renovate! - dependencies updates:
  • Updated dependency tslib@~2.5.0 ↗︎ (from ~2.4.0, in dependencies)

dotansimha/graphql-code-generator (@​graphql-codegen/typescript)

v3.0.4

Compare Source

Patch Changes

• Updated dependencies [386cf9044, 402cb8ac0]:
  • @​graphql-codegen/visitor-plugin-common@​3.1.1

v3.0.3

Compare Source

Patch Changes

• #​9150 92d86b009 Thanks @​rliljest! - Properly escape enum identifiers when enumsAsConst is used

• Updated dependencies [e56790104, b7dacb21f, f104619ac, acb647e4e, 9f4d9c5a4]:

  • @​graphql-codegen/visitor-plugin-common@​3.1.0
  • @​graphql-codegen/plugin-helpers@​4.2.0

v3.0.2

Compare Source

Patch Changes

• Updated dependencies [ba0610bbd, 4b49f6fbe, b343626c9]:
  • @​graphql-codegen/visitor-plugin-common@​3.0.2

dotansimha/graphql-code-generator (@​graphql-codegen/typescript-resolvers)

v3.2.1

Compare Source

Patch Changes

• #​9231 402cb8ac0 Thanks @​eddeee888! - Implement resolversNonOptionalTypename for mapper cases

• Updated dependencies [386cf9044, 402cb8ac0]:

  • @​graphql-codegen/visitor-plugin-common@​3.1.1
  • @​graphql-codegen/typescript@​3.0.4

v3.2.0

Compare Source

Minor Changes

• #​9146 9f4d9c5a4 Thanks @​eddeee888! - [typescript-resolvers] Add resolversNonOptionalTypename config option.

  This is extending on ResolversUnionTypes implemented in https://github.com/dotansimha/graphql-code-generator/pull/9069

  resolversNonOptionalTypename adds non-optional __typename to union members of ResolversUnionTypes, without affecting the union members' base intefaces.

  A common use case for non-optional __typename of union members is using it as the common field to work out the final schema type. This makes implementing the union's __resolveType very simple as we can use __typename to decide which union member the resolved object is. Without this, we have to check the existence of field/s on the incoming object which could be verbose.

  For example, consider this schema:

  type Query {
    book(id: ID!): BookPayload!
  }
  
  type Book {
    id: ID!
    isbn: String!
  }
  
  type BookResult {
    node: Book
  }
  
  type PayloadError {
    message: String!
  }
  
  union BookPayload = BookResult | PayloadError

  With optional __typename: We need to check existence of certain fields to resolve type in the union resolver:

  // Query/book.ts
  export const book = async () => {
    try {
      const book = await fetchBook();
      // 1. No `__typename` in resolver results...
      return {
        node: book,
      };
    } catch (e) {
      return {
        message: 'Failed to fetch book',
      };
    }
  };
  
  // BookPayload.ts
  export const BookPayload = {
    __resolveType: parent => {
      // 2. ... means more checks in `__resolveType`
      if ('message' in parent) {
        return 'PayloadError';
      }
      return 'BookResult';
    },
  };

  With non-optional __typename: Resolvers declare the type. This which gives us better TypeScript support in resolvers and simplify __resolveType implementation:

  // Query/book.ts
  export const book = async () => {
    try {
      const book = await fetchBook();
      // 1. `__typename` is declared in resolver results...
      return {
        __typename: 'BookResult', // 1a. this also types `node` for us 🎉
        node: book,
      };
    } catch (e) {
      return {
        __typename: 'PayloadError',
        message: 'Failed to fetch book',
      };
    }
  };
  
  // BookPayload.ts
  export const BookPayload = {
    __resolveType: parent => parent.__typename, // 2. ... means a very simple check in `__resolveType`
  };

  Using resolversNonOptionalTypename: add it into typescript-resolvers plugin config:

  // codegen.ts
  const config: CodegenConfig = {
    schema: 'src/schema/**/*.graphql',
    generates: {
      'src/schema/types.ts': {
        plugins: ['typescript', 'typescript-resolvers'],
        config: {
          resolversNonOptionalTypename: true, // Or `resolversNonOptionalTypename: { unionMember: true }`
        },
      },
    },
  };

Patch Changes

• #​9206 e56790104 Thanks @​eddeee888! - Fix ResolversUnionTypes being used in ResolversParentTypes

  Previously, objects with mappable fields are converted to Omit format that references its own type group or ResolversTypes or ResolversParentTypes e.g.

  export type ResolversTypes = {
    Book: ResolverTypeWrapper<BookMapper>;
    BookPayload: ResolversTypes['BookResult'] | ResolversTypes['StandardError'];
    // Note: `result` on the next line references `ResolversTypes["Book"]`
    BookResult: ResolverTypeWrapper<Omit<BookResult, 'result'> & { result?: Maybe<ResolversTypes['Book']> }>;
    StandardError: ResolverTypeWrapper<StandardError>;
  };
  
  export type ResolversParentTypes = {
    Book: BookMapper;
    BookPayload: ResolversParentTypes['BookResult'] | ResolversParentTypes['StandardError'];
    // Note: `result` on the next line references `ResolversParentTypes["Book"]`
    BookResult: Omit<BookResult, 'result'> & { result?: Maybe<ResolversParentTypes['Book']> };
    StandardError: StandardError;
  };

  In https://github.com/dotansimha/graphql-code-generator/pull/9069, we extracted resolver union types to its own group:

  export type ResolversUnionTypes = {
    // Note: `result` on the next line references `ResolversTypes["Book"]` which is only correct for the `ResolversTypes` case
    BookPayload: (Omit<BookResult, 'result'> & { result?: Maybe<ResolversTypes['Book']> }) | StandardError;
  };
  
  export type ResolversTypes = {
    Book: ResolverTypeWrapper<BookMapper>;
    BookPayload: ResolverTypeWrapper<ResolversUnionTypes['BookPayload']>;
    BookResult: ResolverTypeWrapper<Omit<BookResult, 'result'> & { result?: Maybe<ResolversTypes['Book']> }>;
    StandardError: ResolverTypeWrapper<StandardError>;
  };
  
  export type ResolversParentTypes = {
    Book: BookMapper;
    BookPayload: ResolversUnionTypes['BookPayload'];
    BookResult: Omit<BookResult, 'result'> & { result?: Maybe<ResolversParentTypes['Book']> };
    StandardError: StandardError;
  };

  This change creates an extra ResolversUnionParentTypes that is referenced by ResolversParentTypes to ensure backwards compatibility:

  export type ResolversUnionTypes = {
    BookPayload: (Omit<BookResult, 'result'> & { result?: Maybe<ResolversParentTypes['Book']> }) | StandardError;
  };
  
  // ... and the reference is changed in ResolversParentTypes:
  export type ResolversParentTypes = {
    // ... other fields
    BookPayload: ResolversUnionParentTypes['BookPayload'];
  };

• f104619ac Thanks @​saihaj! - Resolve issue with nesting fields in @provides directive being prevented

• Updated dependencies [e56790104, b7dacb21f, f104619ac, 92d86b009, acb647e4e, 9f4d9c5a4]:

  • @​graphql-codegen/visitor-plugin-common@​3.1.0
  • @​graphql-codegen/plugin-helpers@​4.2.0
  • @​graphql-codegen/typescript@​3.0.3

v3.1.1

Compare Source

Patch Changes

• #​9110 ba0610bbd Thanks @​gilgardosh! - Custom mappers with placeholder will apply omit

• #​9069 4b49f6fbe Thanks @​eddeee888! - Extract union types to ResolversUnionTypes

• Updated dependencies [ba0610bbd, 4b49f6fbe, b343626c9]:

  • @​graphql-codegen/visitor-plugin-common@​3.0.2
  • @​graphql-codegen/typescript@​3.0.2

nuxt/devtools

v0.5.0

Compare Source

Bug Fixes

• build-analyze: improve ui (bd263ee)
• components: improve graph relationship filtering, close #​192 (c27f80b)
• debounce disconnect indicator (895e6e3)
• devtools-ui-kit: update unocss config path (#​238) (5162bdd)
• double disable vue-inspector (9dc0694)
• improve module meta resolution (7dc3d93)
• install-module: process exit code (8c8097e)
• open-graph: avoid layout shift (4b1eb2c)
• open-graph: use description for facebook (#​239) (31c92f5)
• print error on process failing (37f690b)
• style: switch, radio, checkbox hover style (#​230) (97f5b1a)
• uninstall modules (#​229) (f7db6a2)

Features

• add component inspect button to the sidebar (512d852)
• add dark/light mode switch transition (#​224) (782e0da)
• allow override vue-inspector options, close #​234 (3311f11)
• components: add legend for graph (de6a97d)
• display vue version, close #​236 (83b775a)
• experimental add module from DevTools (#​222) (501682b)
• experimental build analyze (#​190) (2344afd)
• isolate ui options per-project (#​232) (3b99477)
• open-graph: use useSeoMeta over useHead (f7d11ee)
• refactor components, close #​227 (0caa4de)
• server-routes: rolling out of experiment state (ed87dfd)
• sidenav overflow as popup (da6c29f)
• ui: fullscreen disconnect indicator (a158b1b)

0.4.6 (2023-05-08)

Bug Fixes

• default state of DockingPanel (a009866)
• DockingPanel clickoutside on iframe (#​211) (afdaa5b)
• fix shortcut to togglePanel (#​212) (e64dbcd)
• nitro storage link (#​220) (ddd2e41)

Features

• add open graph tab (#​209) (b94de30)
• allow iframe permissions (#​215) (44fce14)

0.4.5 (2023-04-30)

Bug Fixes

• correctly read plugins list (76bc71d)
• use compile time markdown (f9979b9)

0.4.4 (2023-04-30)

Features

• open in file in embeded vscode (#​207) (9f17662)

0.4.3 (2023-04-29)

Bug Fixes

• disconnect indicator zindex, close #​202 (e9ab49f)
• server-routes watcher (#​205) (19fda12)
• wizard: update disable logic (95353b6)
• wizard: use object options instead, close #​206 (d63cf58)

Features

• improve settings ui (c0b4bd6)
• support middleware, close #​184 (73ef44c)
• support navigating to virtual file (ff27b92)

0.4.2 (2023-04-24)

Bug Fixes

• code style (4a082d1)
• components in graph view style (#​197) (3075fc1)
• ui layout (eeb1744)
• ui: sidenav tooltip overlaps with title (#​199) (aec5192)
• wizard: builtin enable setup fails on new installs (#​200) (9551479)

Features

• add more categories (3d41495)
• categorize tabs (64c48cd)
• help page for each tab (#​194) (5ce8df3)
• plugins: add total execution time (2cbb52e)
• support tab badge (80a5ba2)
• syncing color mode backward for iframe, close #​195 (76b3c7a)

Performance Improvements

• defer devtools client initialization (2949e0d)
• defer devtools client loading (ebc9a38)
• improve runtime icons render (ea37a07)

0.4.1 (2023-04-18)

Bug Fixes

• fix domain to work with https (#​178) (646fb9b)
• server-routes: add method dropdown (#​187) (f47060e)
• server-routes: handle base url (06eb4d7)
• server-routes: persistence between route switches (#​186) (2791d3e)
• ServerRouteDetail: fix domain port & body (#​185) (7b1fbf1)
• ui-kit: NTextInput styles (0ed638e)
• ui-kit: ssr compatibility, close #​183 (4f49cd4)

Features

• provide docs for built-in composables (e32b8d5)
• server-routes: more code snippets (40913b9)
• server-routes: open route in editor button (#​189) (c0cbfdb)
• styling (4be0a97)
• ui-kit: Make NTextInput more generic (#​181) (f3d61da)

v0.4.6

Compare Source

Bug Fixes

• default state of DockingPanel (a009866)
• DockingPanel clickoutside on iframe (#​211) (afdaa5b)
• fix shortcut to togglePanel (#​212) (e64dbcd)
• nitro storage link (#​220) (ddd2e41)

Features

• add open graph tab (#​209) (b94de30)
• allow iframe permissions (#​215) (44fce14)

v0.4.5

Compare Source

Bug Fixes

• correctly read plugins list (76bc71d)
• use compile time markdown (f9979b9)

v0.4.4

Compare Source

Features

• open in file in embeded vscode (#​207) (9f17662)

v0.4.3

Compare Source

Bug Fixes

• disconnect indicator zindex, close #​202 (e9ab49f)
• server-routes watcher (#​205) (19fda12)
• wizard: update disable logic (95353b6)
• wizard: use object options instead, close #​206 (d63cf58)

Features

• improve set

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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-commenter]

Codecov Report

Merging #47 (6a30fd3) into main (e226623) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #47   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines           10        10           
  Branches         2         2           
=========================================
  Hits            10        10           

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[renovate]

⚠ 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: pnpm-lock.yaml

installing v2 tool node v18.16.0
linking tool node v18.16.0
node: v18.16.0 /usr/local/bin/node
npm: 9.5.1  /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 8 seconds
installing v2 tool pnpm v8.0.0
linking tool pnpm v8.0.0
8.0.0
Installed v2 /usr/local/buildpack/tools/v2/pnpm.sh in 4 seconds
Scope: all 2 projects

   ╭─────────────────────────────────────────────────────────────────╮
   │                                                                 │
   │                Update available! 8.0.0 → 8.5.1.                 │
   │   Changelog: https://github.com/pnpm/pnpm/releases/tag/v8.5.1   │
   │                Run "pnpm add -g pnpm" to update.                │
   │                                                                 │
   │     Follow @pnpmjs for updates: https://twitter.com/pnpmjs      │
   │                                                                 │
   ╰─────────────────────────────────────────────────────────────────╯

Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 12, reused 0, downloaded 0, added 0
Progress: resolved 19, reused 0, downloaded 0, added 0
Progress: resolved 21, reused 0, downloaded 0, added 0
Progress: resolved 23, reused 0, downloaded 3, added 0
Progress: resolved 26, reused 0, downloaded 7, added 0
Progress: resolved 26, reused 0, downloaded 18, added 0
Progress: resolved 27, reused 0, downloaded 20, added 0
Progress: resolved 27, reused 0, downloaded 21, added 0
Progress: resolved 27, reused 0, downloaded 23, added 0
Progress: resolved 27, reused 0, downloaded 26, added 0
Progress: resolved 27, reused 0, downloaded 27, added 0
Progress: resolved 48, reused 0, downloaded 27, added 0
Progress: resolved 68, reused 0, downloaded 45, added 0
Progress: resolved 87, reused 0, downloaded 68, added 0
Progress: resolved 109, reused 0, downloaded 84, added 0
Progress: resolved 126, reused 0, downloaded 101, added 0
Progress: resolved 148, reused 0, downloaded 123, added 0
Progress: resolved 161, reused 0, downloaded 138, added 0
Progress: resolved 170, reused 0, downloaded 139, added 0
Progress: resolved 180, reused 0, downloaded 151, added 0
Progress: resolved 197, reused 0, downloaded 164, added 0
Progress: resolved 219, reused 0, downloaded 186, added 0
Progress: resolved 234, reused 0, downloaded 203, added 0
Progress: resolved 247, reused 0, downloaded 218, added 0
Progress: resolved 256, reused 0, downloaded 227, added 0
Progress: resolved 262, reused 0, downloaded 230, added 0
Progress: resolved 264, reused 0, downloaded 234, added 0
Progress: resolved 274, reused 0, downloaded 241, added 0
Progress: resolved 294, reused 0, downloaded 261, added 0
Progress: resolved 317, reused 0, downloaded 280, added 0
Progress: resolved 329, reused 0, downloaded 293, added 0
Progress: resolved 356, reused 0, downloaded 317, added 0
Progress: resolved 368, reused 0, downloaded 326, added 0
Progress: resolved 377, reused 0, downloaded 338, added 0
Progress: resolved 383, reused 0, downloaded 348, added 0
Progress: resolved 390, reused 0, downloaded 351, added 0
Progress: resolved 405, reused 0, downloaded 365, added 0
Progress: resolved 432, reused 0, downloaded 386, added 0
Progress: resolved 456, reused 0, downloaded 408, added 0
Progress: resolved 479, reused 0, downloaded 430, added 0
Progress: resolved 491, reused 0, downloaded 443, added 0
Progress: resolved 506, reused 0, downloaded 457, added 0
Progress: resolved 524, reused 0, downloaded 472, added 0
Progress: resolved 535, reused 0, downloaded 478, added 0
Progress: resolved 559, reused 0, downloaded 504, added 0
Progress: resolved 607, reused 0, downloaded 535, added 0
Progress: resolved 628, reused 0, downloaded 549, added 0
Progress: resolved 640, reused 0, downloaded 561, added 0
Progress: resolved 656, reused 0, downloaded 577, added 0
Progress: resolved 678, reused 0, downloaded 597, added 0
Progress: resolved 701, reused 0, downloaded 614, added 0
Progress: resolved 729, reused 0, downloaded 640, added 0
Progress: resolved 747, reused 0, downloaded 665, added 0
Progress: resolved 757, reused 0, downloaded 677, added 0
Progress: resolved 774, reused 0, downloaded 690, added 0
Progress: resolved 804, reused 0, downloaded 692, added 0
Progress: resolved 816, reused 0, downloaded 707, added 0
Progress: resolved 840, reused 0, downloaded 726, added 0
Progress: resolved 869, reused 0, downloaded 753, added 0
Progress: resolved 898, reused 0, downloaded 780, added 0
Progress: resolved 928, reused 0, downloaded 809, added 0
Progress: resolved 950, reused 0, downloaded 827, added 0
Progress: resolved 976, reused 0, downloaded 849, added 0
Progress: resolved 990, reused 0, downloaded 872, added 0
Progress: resolved 1013, reused 0, downloaded 887, added 0
Progress: resolved 1041, reused 0, downloaded 912, added 0
Progress: resolved 1057, reused 0, downloaded 931, added 0
.                                        |  WARN  deprecated @npmcli/move-file@2.0.1
Progress: resolved 1093, reused 0, downloaded 963, added 0
Progress: resolved 1122, reused 0, downloaded 985, added 0
.                                        |  WARN  deprecated stringify-package@1.0.1
Progress: resolved 1151, reused 0, downloaded 1008, added 0
Progress: resolved 1161, reused 0, downloaded 1017, added 0
Progress: resolved 1176, reused 0, downloaded 1041, added 0
Progress: resolved 1180, reused 0, downloaded 1072, added 0
Progress: resolved 1180, reused 0, downloaded 1103, added 0
Progress: resolved 1194, reused 0, downloaded 1139, added 0
Progress: resolved 1232, reused 0, downloaded 1166, added 0
Progress: resolved 1252, reused 0, downloaded 1194, added 0
Progress: resolved 1275, reused 0, downloaded 1228, added 0
Progress: resolved 1275, reused 0, downloaded 1229, added 0
Progress: resolved 1294, reused 0, downloaded 1248, added 0
undefined
 ERR_PNPM_PATCH_NOT_APPLIED  The following patches were not applied: tslib@2.4.1

Either remove them from "patchedDependencies" or update them to match packages in your dependencies.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠ Warning: custom changes will be lost.