@graphprotocol/[email protected]

Patch Changes

• 074d9b8: Upgrade internal GraphQL-Mesh deps to have better cross-platform support (node/browser)
• 074d9b8: Improve logging experience
• 074d9b8: Update internal dependencies
• 074d9b8: Use GraphQL Yoga internally in Mesh CLI and have an improved execution layer
• 074d9b8: Update internal GraphQL Mesh dependecies in order to allow custom package prefixes besides @graphql-mesh/*
• 074d9b8: Update core GraphQL-Mesh version for a better compatibility for browser/Node envs
• 074d9b8: Update internal GraphiQL and have better interal GraphQL server (based on Yoga) in CLI commands
• 074d9b8: Bump internal GraphQL-Tools deps for an improve error handling
• Updated dependencies [063dc0b]
• Updated dependencies [063dc0b]
  • @graphprotocol/[email protected]
  • @graphprotocol/[email protected]

@graphprotocol/[email protected]

Patch Changes

• 063dc0b: #### Block Tracking Transform

  graph-client implements automatic block tracking using number_gte filter of graph-node. This automates the process of fetching and tracking the block number of entites.

  This feature is implemented in @graphprotocol/client-block-tracking and installed automatically with the graph-client CLI package.

  Usage Example

  # .graphclientrc.yml
  sources:
    - name: uniswap
      handler:
        graphql:
          endpoint: https://api.thegraph.com/subgraphs/name/uniswap/uniswap-v2
      transforms: # The following section will make sure to automatically fetch the block information, and then use it for tracking in future queries.
        - blockTracking:
            validateSchema: true # Validates that the schema source actually contains _meta and input block filters.

@graphprotocol/[email protected]

Patch Changes

• 063dc0b: #### Auto Pagination Transform

  graph-client implements automatic pagination using first: and after: filters of graph-node.

  At the moment, graph-node allow fetching only 1000 records per query. This transfomer allow you to run queries with any limit, and the breaks it automatically to multiple concurrent requests, then merges the responses into a single response.

  This feature is implemented in @graphprotocol/client-auto-pagination and installed automatically with the graph-client CLI package.

  Usage Example

  # .graphclientrc.yml
  sources:
    - name: uniswap
      handler:
        graphql:
          endpoint: https://api.thegraph.com/subgraphs/name/uniswap/uniswap-v2
      transforms:
        - autoPagination:
            validateSchema: true # Validates that the schema source actually contains the required input filters.
            limitOfRecords: 1000 # Default is 1000, you can change if you indexer has different configuration in GRAPH_GRAPHQL_MAX_FIRST var.

@graphprotocol/[email protected]

Patch Changes

• 563dcc5: Fix issues with NextJS compatibility

@graphprotocol/[email protected]

Patch Changes

• 074d9b8: Update internal dependencies

@graphprotocol/[email protected]

Patch Changes

• cc01355: Fix Browser compatibility issues

@graphprotocol/[email protected]

Patch Changes

• ca60361: Update core dependencies to latest versions

@graphprotocol/[email protected]

Patch Changes

• ca60361: Update core dependencies to latest versions

@graphprotocol/[email protected]

Patch Changes

• ca60361: Update core dependencies to latest versions

@graphprotocol/[email protected]

Patch Changes

• dcdec54: Bump graph-mesh version to fix output issues under index.ts