chore: update npm dependencies by renovate[bot] · Pull Request #6 · reearth/core

renovate · 2024-05-04T00:22:00Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update	Pending
@apollo/client (source)	`3.8.1` → `4.2.0`	devDependencies	major	`4.2.2` (+1)
@chromatic-com/storybook	`^1.3.3` → `^5.2.1`	devDependencies	major
@emotion/jest (source)	`11.11.0` → `11.14.2`	devDependencies	minor
@reearth/cesium-mvt-imagery-provider	`1.5.4` → `1.6.2`	dependencies	minor
@storybook/addon-essentials (source)	`8.0.8` → `8.6.14`	devDependencies	minor
@storybook/addon-interactions (source)	`8.0.8` → `8.6.14`	devDependencies	minor
@storybook/addon-links (source)	`8.0.8` → `10.4.1`	devDependencies	major	`10.4.2`
@storybook/addon-onboarding (source)	`8.0.8` → `10.4.1`	devDependencies	major	`10.4.2`
@storybook/blocks (source)	`8.0.8` → `8.6.14`	devDependencies	minor
@storybook/react (source)	`8.0.8` → `10.4.1`	devDependencies	major	`10.4.2`
@storybook/react-vite (source)	`8.0.8` → `10.4.1`	devDependencies	major	`10.4.2`
@storybook/test (source)	`8.0.8` → `8.6.15`	devDependencies	minor
@testing-library/jest-dom	`6.1.4` → `6.9.1`	devDependencies	minor
@testing-library/react	`14.0.0` → `16.3.2`	devDependencies	major
@turf/invariant	`6.5.0` → `7.3.5`	dependencies	major
@turf/turf	`6.5.0` → `7.3.5`	dependencies	major
@types/geojson (source)	`7946.0.14` → `7946.0.16`	devDependencies	patch
@types/js-md5 (source)	`0.7.2` → `0.8.0`	devDependencies	minor
@types/node (source)	`20.12.7` → `24.12.4`	devDependencies	major	`24.13.1` (+1)
@types/proj4	`2.5.5` → `2.19.0`	dependencies	minor
@types/react (source)	`18.2.6` → `19.2.15`	devDependencies	major	`19.2.17` (+1)
@types/react-dom (source)	`18.2.6` → `19.2.3`	devDependencies	major
@types/uuid	`9.0.8` → `11.0.0`	devDependencies	major
@typescript-eslint/eslint-plugin (source)	`7.2.0` → `8.60.0`	devDependencies	major	`8.60.1`
@typescript-eslint/parser (source)	`7.2.0` → `8.60.0`	devDependencies	major	`8.60.1`
@vitejs/plugin-react (source)	`4.2.1` → `6.0.2`	devDependencies	major
@xstate/react (source)	`3.2.1` → `6.1.0`	dependencies	major
csv-parse (source)	`5.5.2` → `6.2.1`	dependencies	major
eslint (source)	`8.57.0` → `10.4.1`	devDependencies	major
eslint-config-reearth	`0.3.0` → `0.4.0`	devDependencies	minor
eslint-plugin-react-hooks (source)	`4.6.0` → `7.1.1`	devDependencies	major
eslint-plugin-react-refresh	`0.4.6` → `0.5.2`	devDependencies	minor
eslint-plugin-storybook (source)	`0.8.0` → `10.4.1`	devDependencies	major	`10.4.2`
fast-xml-parser	`4.3.2` → `5.8.0`	dependencies	major
framer-motion	`11.0.27` → `12.40.0`	dependencies	major
jackspeak	`2.1.1` → `4.2.3`	resolutions	major
jotai	`1.12.1` → `2.20.0`	dependencies	major
js-md5	`0.7.3` → `0.8.3`	dependencies	minor
jsdom	`22.1.0` → `29.1.1`	devDependencies	major
jsep (source)	`1.3.8` → `1.4.0`	dependencies	minor
jsonpath-plus	`7.2.0` → `10.4.0`	dependencies	major
lodash-es (source)	`4.17.21` → `4.18.1`	dependencies	minor
lru-cache	`8.0.4` → `11.5.1`	dependencies	major
node (source)	`>=20` → `>=24.16.0`	engines	major
pbf	`3.2.1` → `5.1.0`	dependencies	major
prettier (source)	`3.2.5` → `3.8.3`	devDependencies	minor
proj4 (source)	`2.11.0` → `2.20.8`	dependencies	minor
protomaps	`1.23.1` → `2.0.1`	dependencies	major
react (source)	`^18.2.0` → `^19.2.6`	peerDependencies	major	`19.2.7`
react (source)	`18.2.0` → `19.2.6`	devDependencies	major	`19.2.7`
react-dom (source)	`^18.2.0` → `^19.2.6`	peerDependencies	major	`19.2.7`
react-dom (source)	`18.2.0` → `19.2.6`	devDependencies	major	`19.2.7`
react-error-boundary (source)	`4.0.11` → `6.1.2`	dependencies	major
react-use	`17.5.0` → `17.6.0`	dependencies	minor
resium	`1.17.4` → `1.22.0`	dependencies	minor	`1.23.0`
storybook (source)	`8.0.8` → `10.4.1`	devDependencies	major	`10.4.2`
typescript (source)	`5.2.2` → `6.0.3`	devDependencies	major
use-callback-ref	`1.3.2` → `1.3.3`	dependencies	patch
use-custom-compare	`1.4.0` → `1.5.0`	dependencies	minor
uuid	`9.0.1` → `14.0.0`	dependencies	major
vite (source)	`5.0.8` → `8.0.14`	devDependencies	major	`8.0.16` (+1)
vite-plugin-dts (source)	`3.8.1` → `5.0.1`	devDependencies	major	`5.0.2`
vite-plugin-svgr	`4.2.0` → `5.2.0`	devDependencies	major
vite-tsconfig-paths	`^4.3.2` → `^6.1.1`	devDependencies	major
vitest (source)	`1.0.4` → `4.1.7`	devDependencies	major	`4.1.8`
web-streams-polyfill	`3.2.1` → `4.3.0`	devDependencies	major
xstate (source)	`4.38.2` → `5.32.0`	dependencies	major

Release Notes

apollographql/apollo-client (@apollo/client)

`v4.2.0`

Compare Source

Minor Changes

#13132 f3ce805 Thanks @phryneas! - Introduce "classic" and "modern" method and hook signatures.

Apollo Client 4.2 introduces two signature styles for methods and hooks. All signatures previously present are now "classic" signatures, and a new set of "modern" signatures are added alongside them.

Classic signatures are the default and are identical to the signatures before Apollo Client 4.2, preserving backward compatibility. Classic signatures still work with manually specified TypeScript generics (e.g., useSuspenseQuery<MyData>(...)). However, manually specifying generics has been discouraged for a long time—instead, we recommend using TypedDocumentNode to automatically infer types, which provides more accurate results without any manual annotations.

Modern signatures automatically incorporate your declared defaultOptions into return types, providing more accurate types. Modern signatures infer types from the document node and do not support manually passing generic type arguments; TypeScript will produce a type error if you attempt to do so.

Methods and hooks automatically switch to modern signatures the moment any non-optional property is declared in DeclareDefaultOptions. The switch happens across all methods and hooks globally:
```
// apollo.d.ts
import "@&#8203;apollo/client";
declare module "@&#8203;apollo/client" {
  namespace ApolloClient {
    namespace DeclareDefaultOptions {
      interface WatchQuery {
        errorPolicy: "all"; // non-optional → modern signatures activated automatically
      }
    }
  }
}
```
Users can also manually switch to modern signatures without declaring any defaultOptions, for example when wanting accurate type inference without relying on global defaultOptions:
```
// apollo.d.ts
import "@&#8203;apollo/client";
declare module "@&#8203;apollo/client" {
  export interface TypeOverrides {
    signatureStyle: "modern";
  }
}
```
Users can do a global DeclareDefaultOptions type augmentation and then manually switch back to "classic" for migration purposes:
```
// apollo.d.ts
import "@&#8203;apollo/client";
declare module "@&#8203;apollo/client" {
  export interface TypeOverrides {
    signatureStyle: "classic";
  }
}
```
Note that this is not recommended for long-term use. When combined with DeclareDefaultOptions, switching back to classic results in the same incorrect types as before Apollo Client 4.2—methods and hooks will not reflect the defaultOptions you've declared.
#13130 dd12231 Thanks @jerelmiller! - Improve the accuracy of client.query return type to better detect the current errorPolicy. The data property is no longer nullable when the errorPolicy is none. This makes it possible to remove the undefined checks or optional chaining in most cases.

#13210 1f9a428 Thanks @jerelmiller! - Add support for automatic event-based refetching, such as window focus.

The RefetchEventManager class handles automatic refetches in response to events. Apollo Client provides built-in sources for window focus and network reconnect as windowFocusSource and onlineSource.

Event refetching is fully opt-in. Create and pass a RefetchEventManager instance to the ApolloClient constructor to activate the event listeners.

import {
  ApolloClient,
  InMemoryCache,
  RefetchEventManager,
  windowFocusSource,
  onlineSource,
} from "@&#8203;apollo/client";

const client = new ApolloClient({
  link,
  cache: new InMemoryCache(),
  refetchEventManager: new RefetchEventManager({
    sources: {
      // Refetch when window is focused
      windowFocus: windowFocusSource,

      // Refetch when the user comes back online
      online: onlineSource,
    },
  }),
});

By default, all active queries refetch when the events fire. Queries can opt out per-event or disable all event refetches:

// Skip refetch on window focus for this query, but keep `online`
useQuery(QUERY, {
  refetchOn: { windowFocus: false },
});

// Disable all event-driven refetches for this query
useQuery(OTHER_QUERY, {
  refetchOn: false,
});

// Enable every event for this query, regardless of defaultOptions
useQuery(LIVE_DASHBOARD, {
  refetchOn: true,
});

// Dynamically enable or disable a refetch when the event fires
useQuery(LIVE_DASHBOARD, {
  refetchOn: ({ source, payload }) => {
    if (source === "windowFocus") {
      // payload is the data associated with the event
      return someCondition(payload);
    }

    return true;
  },
});

// Dynamically enable or disable a refetch for a specific event
useQuery(LIVE_DASHBOARD, {
  refetchOn: {
    windowFocus: ({ payload }) => {
      // payload is the data associated with the event
      return someCondition(payload);
    },
  },
});

To enable per-query opt-in rather than opt-out, set defaultOptions.watchQuery.refetchOn to false and enable it per-query instead.

const client = new ApolloClient({
  link,
  cache,
  refetchEventManager: new RefetchEventManager({
    sources: { windowFocus: windowFocusSource },
  }),
  defaultOptions: {
    watchQuery: { refetchOn: false },
  },
});

// Only this query refetches on window focus
useQuery(DASHBOARD_QUERY, { refetchOn: { windowFocus: true } });

When defaultOptions.watchQuery.refetchOn and per-query refetchOn options are provided, the objects are merged together.

Custom events

You can also add your own custom events that trigger refetches. Register your event name and payload type using TypeScript module augmentation, then provide a source function that returns an Observable. The source's emitted value becomes the event's payload.

import { Observable } from "@&#8203;apollo/client";
import { filter } from "rxjs";
import { AppState, AppStateStatus, Platform } from "react-native";

declare module "@&#8203;apollo/client" {
  interface RefetchEvents {
    reactNativeAppStatus: AppStateStatus;
  }
}

const refetchEventManager = new RefetchEventManager({
  sources: {
    reactNativeAppStatus: () => {
      return new Observable((observer) => {
        const subscription = AppState.addEventListener("change", (status) => {
          observer.next(status);
        });
        return () => subscription.remove();
      }).pipe(
        filter((status) => Platform.OS !== "web" && status === "active")
      );
    },
  },
});

// Disable per-query by setting the event to false
useQuery(QUERY, { refetchOn: { reactNativeAppStatus: false } });

Manually trigger an event refetch

Refetches can be triggered imperatively by calling emit with the event name and its payload (if any).

refetchEventManager.emit("reactNativeAppStatus", "active");

Sourceless events

A source that has no automatic detection logic but still wants imperative emit support can be declared as true. Type the event as void to omit the payload argument.

declare module "@&#8203;apollo/client" {
  interface RefetchEvents {
    userTriggered: void;
  }
}

const refetchEventManager = new RefetchEventManager({
  sources: { userTriggered: true },
});

refetchEventManager.emit("userTriggered");

Note: Calling emit on an event without a registered source will log a warning and result in a no-op.

Custom handlers

When an event fires, the default handler calls client.refetchQueries({ include: "active" }) filtered by each query's refetchOn setting. You can override the handler for an event to add your own custom filtering. For example, to refetch all queries, including standby queries, define a handler for the event:

const refetchEventManager = new RefetchEventManager({
  // ...
  handlers: {
    userTriggered: ({ client, source, payload, matchesRefetchOn }) => {
      return client.refetchQueries({
        include: "all",
        onQueryUpdated: (observableQuery) => {
          return matchesRefetchOn(observableQuery);
        },
      });
    },
  },
});

Handlers must return either a RefetchQueriesResult or void. Returning void skips refetching for the event.

#13232 f1b541f Thanks @jerelmiller! - Version bump to rc.
#13206 08fccab Thanks @jerelmiller! - Extend the defaultOptions type-safety work to client.mutate and useMutation.

The errorPolicy option now flows through to the result types for mutations in the same way it already does for queries:
- ApolloClient.MutateResult<TData, TErrorPolicy> maps errorPolicy to the concrete shape of data and error:
  - "none" → { data: TData; error?: never }
  - "all" → { data: TData | undefined; error?: ErrorLike }
  - "ignore" → { data: TData | undefined; error?: never }
- client.mutate and useMutation pick up the declared defaultOptions.mutate.errorPolicy and the explicit errorPolicy on each call to narrow return types accordingly.
- useMutation.Result.error is narrowed to undefined when errorPolicy is "ignore", since client.mutate never resolves with an error in that case.
DeclareDefaultOptions.Mutate already accepted errorPolicy; the new behavior is that once you declare it, hook and method return types reflect it:
```
// apollo.d.ts
import "@&#8203;apollo/client";

declare module "@&#8203;apollo/client" {
  namespace ApolloClient {
    namespace DeclareDefaultOptions {
      interface Mutate {
        errorPolicy: "all";
      }
    }
  }
}
```
```
const result = await client.mutate({ mutation: MUTATION });
result.data;
//     ^? TData | undefined
result.error;
//     ^? ErrorLike | undefined
```
Setting errorPolicy on an individual call overrides the default for that call's return type.

#13222 b93c172 Thanks @jerelmiller! - Extend the defaultOptions type-safety work to preloadQuery (returned from createQueryPreloader). Defaults declared in DeclareDefaultOptions.WatchQuery now work with preloadQuery to ensure the PreloadedQueryRef's data states are correctly set.

// apollo.d.ts
import "@&#8203;apollo/client";

declare module "@&#8203;apollo/client" {
  namespace ApolloClient {
    namespace DeclareDefaultOptions {
      interface WatchQuery {
        errorPolicy: "all";
      }
    }
  }
}

const preloadQuery = createQueryPreloader(client);
const queryRef = preloadQuery(QUERY);
//    ^? PreloadedQueryRef<TData, TVariables, "complete" | "streaming" | "empty">

#13132 f3ce805 Thanks @phryneas! - Synchronize method and hook return types with defaultOptions.

Prior to this change, the following code snippet would always apply:
```
declare const MY_QUERY: TypedDocumentNode<TData, TVariables>;
const result1 = useSuspenseQuery(MY_QUERY);
result1.data;
//      ^? TData
const result2 = useSuspenseQuery(MY_QUERY, { errorPolicy: "all" });
result2.data;
//      ^? TData | undefined
```
While these types are generally correct, if you were to set errorPolicy: 'all' as a default option, the type of result.data for the first query would remain TData instead of changing to TData | undefined to match the runtime behavior.

We are now enforcing that certain defaultOptions types need to be registered globally. This means that if you want to use errorPolicy: 'all' as a default option for a query, you will need to register its type like this:
```
// apollo.d.ts
import "@&#8203;apollo/client";

declare module "@&#8203;apollo/client" {
  namespace ApolloClient {
    namespace DeclareDefaultOptions {
      interface WatchQuery {
        // possible global-registered values:
        // * `errorPolicy`
        // * `returnPartialData`
        errorPolicy: "all";
      }
      interface Query {
        // possible global-registered values:
        // * `errorPolicy`
      }
      interface Mutate {
        // possible global-registered values:
        // * `errorPolicy`
      }
    }
  }
}
```
Once this type declaration is in place, the type of result.data in the above example will correctly be changed to TData | undefined, reflecting the possibility that if an error occurs, data might be undefined. Manually specifying useSuspenseQuery(MY_QUERY, { errorPolicy: "none" }); changes result.data to TData to reflect the local override.

This change means that you will need to declare your default options types in order to use defaultOptions with ApolloClient, otherwise you will see a TypeScript error.

Without the type declaration, the following (previously valid) code will now error:
```
new ApolloClient({
  link: ApolloLink.empty(),
  cache: new InMemoryCache(),
  defaultOptions: {
    watchQuery: {
      // results in a type error:
      // Type '"all"' is not assignable to type '"A default option for watchQuery.errorPolicy must be declared in ApolloClient.DeclareDefaultOptions before usage. See https://www.apollographql.com/docs/react/data/typescript#declaring-default-options-for-type-safety."'.
      errorPolicy: "all",
    },
  },
});
```
If you are creating multiple instances of Apollo Client with conflicting default options and you cannot register a single defaultOptions value as a result, you can relax the constraints by declaring those options as union types covering all values used by all clients. The properties can be required (to enforce them in defaultOptions) or optional (if some constructor calls won't pass a value):
```
// apollo.d.ts
import "@&#8203;apollo/client";

declare module "@&#8203;apollo/client" {
  export namespace ApolloClient {
    export namespace DeclareDefaultOptions {
      interface WatchQuery {
        errorPolicy?: "none" | "all" | "ignore";
        returnPartialData?: boolean;
      }
      interface Query {
        errorPolicy?: "none" | "all" | "ignore";
      }
      interface Mutate {
        errorPolicy?: "none" | "all" | "ignore";
      }
    }
  }
}
```
With this declaration, the ApolloClient constructor accepts any of those values in defaultOptions. The tradeoff is that hook and method return types become more generic. For example, calling useSuspenseQuery without an explicit errorPolicy will return a result typed as if all error policies are possible, since TypeScript can't know which specific value your instance uses at runtime.

Note that making a property optional (errorPolicy?:) is equivalent to adding the TypeScript default value ("none") to the union. So errorPolicy?: "all" | "ignore" has the same effect on return types as errorPolicy: "none" | "all" | "ignore", because TypeScript assumes the option could also be absent (i.e., "none").

You can also use a partial union that only lists the values you actually use. For example, if you only ever use "all" or "ignore", declare errorPolicy: "all" | "ignore" (required) to keep the union narrow and avoid unused values broadening your signatures unnecessarily.

Patch Changes

#13217 790f987 Thanks @jerelmiller! - Fix the deprecation for the classic signatures for function overloads that rely on type inference from a TypedDocumentNode. The deprecation now only applies to classic signatures that provide explicit type arguments to encourage the use of TypedDocumentNode.
#13166 0537d97 Thanks @jerelmiller! - Release changes in 4.1.5 and 4.1.6.
#13215 54c9eb7 Thanks @jerelmiller! - Ensure the options object for the useQuery, useSuspenseQuery, and useBackgroundQuery hooks provide proper IntelliSense suggestions.
#13229 9a7f65a Thanks @jerelmiller! - Fix refetchOn merging when defaultOptions.watchQuery.refetchOn is set to a non-object value (false, true, or a function) and the per-query refetchOn is an object. Previously the per-query object completely replaced the default so unspecified events fell back to "enabled" regardless of the default.

The defaultOptions value now applies to any event the per-query object does not explicitly configure:
- false - unspecified events stay disabled
- true - unspecified events refetch
- Callback function - the function is called for unspecified events to determine whether to refetch
```
const client = new ApolloClient({
  // ...
  defaultOptions: {
    watchQuery: {
      refetchOn: false,
    },
  },
});

// Only `windowFocus` refetches. Other events stay disabled per the default.
useQuery(QUERY, { refetchOn: { windowFocus: true } });
```
#13230 b25b659 Thanks @jerelmiller! - Add the ability to override the default event handler on RefetchEventManager. The default handler runs when no per-source handler is configured for an event. Provide a custom handler via the defaultHandler constructor option or the setDefaultEventHandler instance method.
```
new RefetchEventManager({
  defaultHandler: ({ client, matchesRefetchOn }) => {
    return client.refetchQueries({
      include: "all",
      onQueryUpdated: matchesRefetchOn,
    });
  },
});
```

`v4.1.9`

Compare Source

Patch Changes

#13203 099954b Thanks @copilot-swe-agent! - Remove the workspaces field from the published package.json in dist to avoid Yarn v1 warnings about workspaces requiring private packages.

`v4.1.8`

Compare Source

Patch Changes

#13202 8a51ea6 Thanks @phryneas! - Ship agent skill for usage with @tanstack/intent — the skill is now bundled in the npm package under skills/apollo-client/ and discoverable by intent list.
For more context, see the TanStack Intent QuickStart.

Patch Changes

#12950 5b4f36a Thanks @jerelmiller! - Don't send operationType in the payload sent by GraphQLWsLink.

`v4.0.6`

Compare Source

Patch Changes

#12937 3b0d89b Thanks @phryneas! - Fix a problem with fetchMore where the loading state wouldn't reset if the result wouldn't result in a data update.

`v4.0.5`

Compare Source

Patch Changes

#12920 e2fc385 Thanks @phryneas! - Fix an invariance type error in the MockedResponse type.

`v4.0.4`

Compare Source

Patch Changes

#12892 db8a04b Thanks @jerelmiller! - Prevent unhandled rejections from the promise returned by calling the mutate function from the useMutation hook.
#12899 5352c12 Thanks @phryneas! - Fix an issue when invariant is called by external libraries when no dev error message handler is loaded.
#12895 71f2517 Thanks @jerelmiller! - Support skipToken with useQuery to provide a more type-safe way to skip query execution.
```
import { skipToken, useQuery } from "@&#8203;apollo/client/react";

// Use `skipToken` in
```

✂ Note

PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- "before 3:00 am on monday"
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 was generated by Mend Renovate. View the repository job log.

coderabbitai · 2024-10-24T08:57:09Z

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

Review comments: Directly reply to a review comment made by CodeRabbit. Example:
- I pushed a fix in commit <commit_id>, please review it.
- Explain this complex logic.
- Open a follow-up GitHub issue for this discussion.
Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
- @coderabbitai explain this code block.
- @coderabbitai modularize this function.
PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
- @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
- @coderabbitai read src/utils.ts and explain its main purpose.
- @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
- @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Join our Discord community for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

@coderabbitai pause to pause the reviews on a PR.
@coderabbitai resume to resume the paused reviews.
@coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
@coderabbitai full review to do a full review from scratch and review all the files again.
@coderabbitai summary to regenerate the summary of the PR.
@coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
@coderabbitai resolve resolve all the CodeRabbit review comments.
@coderabbitai configuration to show the current CodeRabbit configuration for the repository.
@coderabbitai help to get help.

Other keywords and placeholders

Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (`.coderabbit.yaml`)

You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
Please see the configuration documentation for more information.
If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

Visit our Documentation for detailed information on how to use CodeRabbit.
Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

renovate Bot force-pushed the renovate/npm branch 16 times, most recently from a1087a0 to 75c8e9c Compare May 11, 2024 11:36

renovate Bot force-pushed the renovate/npm branch 13 times, most recently from 60cb682 to 80600c5 Compare May 18, 2024 23:55

renovate Bot force-pushed the renovate/npm branch from 80600c5 to 6632f29 Compare May 20, 2024 22:27

renovate Bot force-pushed the renovate/npm branch 17 times, most recently from 833ff34 to 08e7299 Compare June 3, 2024 01:16

renovate Bot force-pushed the renovate/npm branch 5 times, most recently from ba4d2f6 to 9d8c7f7 Compare July 8, 2024 23:21

renovate Bot force-pushed the renovate/npm branch 5 times, most recently from 0b275da to 3d7b736 Compare July 16, 2024 21:00

renovate Bot force-pushed the renovate/npm branch from 3d7b736 to 708c99a Compare July 19, 2024 05:44

chore: update npm dependencies

3ac9cb3

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: update npm dependencies#6

chore: update npm dependencies#6
renovate[bot] wants to merge 1 commit into
betafrom
renovate/npm

renovate Bot commented May 4, 2024 •

edited

Loading

Uh oh!

coderabbitai Bot commented Oct 24, 2024 •

edited

Loading

Review skipped

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (`.coderabbit.yaml`)

Documentation and Community

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Conversation

renovate Bot commented May 4, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Minor Changes

Custom events

Manually trigger an event refetch

Sourceless events

Custom handlers

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Patch Changes

Configuration

Uh oh!

coderabbitai Bot commented Oct 24, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Review skipped

Chat

Support

CodeRabbit Commands (Invoked using PR comments)

Other keywords and placeholders

CodeRabbit Configuration File (.coderabbit.yaml)

Documentation and Community

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate Bot commented May 4, 2024 •

edited

Loading

coderabbitai Bot commented Oct 24, 2024 •

edited

Loading

CodeRabbit Configuration File (`.coderabbit.yaml`)