@latticexyz/block-logs-stream@2.0.0-next.3

Patch Changes

• Updated dependencies [bb6ada74, 331f0d63]:
  • @latticexyz/common@2.0.0-next.3
  • @latticexyz/config@2.0.0-next.3
  • @latticexyz/schema-type@2.0.0-next.3

solhint-plugin-mud@2.0.0-next.2

solhint-plugin-mud@2.0.0-next.2

solhint-config-mud@2.0.0-next.2

solhint-config-mud@2.0.0-next.2

create-mud@2.0.0-next.2

Major Changes

• #1278 48c51b52 Thanks @holic! - RECS components are now dynamically created and inferred from your MUD config when using syncToRecs.

  To migrate existing projects after upgrading to this MUD version:

  1. Remove contractComponents.ts from client/src/mud

  2. Remove components argument from syncToRecs

  3. Update build:mud and dev scripts in contracts/package.json to remove tsgen

     - "build:mud": "mud tablegen && mud worldgen && mud tsgen --configPath mud.config.ts --out ../client/src/mud",
     + "build:mud": "mud tablegen && mud worldgen",

     - "dev": "pnpm mud dev-contracts --tsgenOutput ../client/src/mud",
     + "dev": "pnpm mud dev-contracts",

• #1284 939916bc Thanks @holic! - MUD dev tools is updated to latest sync stack. You must now pass in all of its data requirements rather than relying on magic globals.

  import { mount as mountDevTools } from "@latticexyz/dev-tools";
  
  - mountDevTools();
  + mountDevTools({
  +   config,
  +   publicClient,
  +   walletClient,
  +   latestBlock$,
  +   blockStorageOperations$,
  +   worldAddress,
  +   worldAbi,
  +   write$,
  +   // if you're using recs
  +   recsWorld,
  + });

  It's also advised to wrap dev tools so that it is only mounted during development mode. Here's how you do this with Vite:

  // https://vitejs.dev/guide/env-and-mode.html
  if (import.meta.env.DEV) {
    mountDevTools({ ... });
  }

Patch Changes

• #1308 b8a6158d Thanks @holic! - bump viem to 1.6.0

@latticexyz/world@2.0.0-next.2

Patch Changes

• #1278 48c51b52 Thanks @holic! - RECS components are now dynamically created and inferred from your MUD config when using syncToRecs.

  To migrate existing projects after upgrading to this MUD version:

  1. Remove contractComponents.ts from client/src/mud

  2. Remove components argument from syncToRecs

  3. Update build:mud and dev scripts in contracts/package.json to remove tsgen

     - "build:mud": "mud tablegen && mud worldgen && mud tsgen --configPath mud.config.ts --out ../client/src/mud",
     + "build:mud": "mud tablegen && mud worldgen",

     - "dev": "pnpm mud dev-contracts --tsgenOutput ../client/src/mud",
     + "dev": "pnpm mud dev-contracts",

• Updated dependencies [a2588116, 939916bc, b8a6158d, 48c51b52, b8a6158d]:

  • @latticexyz/store@2.0.0-next.2
  • @latticexyz/common@2.0.0-next.2
  • @latticexyz/schema-type@2.0.0-next.2
  • @latticexyz/config@2.0.0-next.2
  • @latticexyz/gas-report@2.0.0-next.2

@latticexyz/utils@2.0.0-next.2

@latticexyz/utils@2.0.0-next.2

@latticexyz/store@2.0.0-next.2

Major Changes

• #1279 a2588116 Thanks @dk1a! - Remove TableId library to simplify store package

Patch Changes

• #1278 48c51b52 Thanks @holic! - RECS components are now dynamically created and inferred from your MUD config when using syncToRecs.

  To migrate existing projects after upgrading to this MUD version:

  1. Remove contractComponents.ts from client/src/mud

  2. Remove components argument from syncToRecs

  3. Update build:mud and dev scripts in contracts/package.json to remove tsgen

     - "build:mud": "mud tablegen && mud worldgen && mud tsgen --configPath mud.config.ts --out ../client/src/mud",
     + "build:mud": "mud tablegen && mud worldgen",

     - "dev": "pnpm mud dev-contracts --tsgenOutput ../client/src/mud",
     + "dev": "pnpm mud dev-contracts",

• Updated dependencies [939916bc, b8a6158d, b8a6158d]:

  • @latticexyz/common@2.0.0-next.2
  • @latticexyz/schema-type@2.0.0-next.2
  • @latticexyz/config@2.0.0-next.2
  • @latticexyz/gas-report@2.0.0-next.2

@latticexyz/store-sync@2.0.0-next.2

Major Changes

• #1278 48c51b52 Thanks @holic! - RECS components are now dynamically created and inferred from your MUD config when using syncToRecs.

  To migrate existing projects after upgrading to this MUD version:

  1. Remove contractComponents.ts from client/src/mud

  2. Remove components argument from syncToRecs

  3. Update build:mud and dev scripts in contracts/package.json to remove tsgen

     - "build:mud": "mud tablegen && mud worldgen && mud tsgen --configPath mud.config.ts --out ../client/src/mud",
     + "build:mud": "mud tablegen && mud worldgen",

     - "dev": "pnpm mud dev-contracts --tsgenOutput ../client/src/mud",
     + "dev": "pnpm mud dev-contracts",

Minor Changes

• #1240 753bdce4 Thanks @holic! - Store sync logic is now consolidated into a createStoreSync function exported from @latticexyz/store-sync. This simplifies each storage sync strategy to just a simple wrapper around the storage adapter. You can now sync to RECS with syncToRecs or SQLite with syncToSqlite and PostgreSQL support coming soon.

  There are no breaking changes if you were just using syncToRecs from @latticexyz/store-sync or running the sqlite-indexer binary from @latticexyz/store-indexer.

Patch Changes

• #1308 b8a6158d Thanks @holic! - bump viem to 1.6.0

• #1302 5294a7d5 Thanks @holic! - Improves support for internal/client-only RECS components

• #1308 b8a6158d Thanks @holic! - remove usages of isNonPendingBlock and isNonPendingLog (fixed with more specific viem types)

• Updated dependencies [a2588116, 939916bc, b8a6158d, 48c51b52, b8a6158d, b8a6158d]:

  • @latticexyz/store@2.0.0-next.2
  • @latticexyz/common@2.0.0-next.2
  • @latticexyz/world@2.0.0-next.2
  • @latticexyz/block-logs-stream@2.0.0-next.2
  • @latticexyz/protocol-parser@2.0.0-next.2
  • @latticexyz/schema-type@2.0.0-next.2
  • @latticexyz/recs@2.0.0-next.2

@latticexyz/store-indexer@2.0.0-next.2

Major Changes

• #1232 b621fb97 Thanks @holic! - Adds a Fastify server in front of tRPC and puts tRPC endpoints under /trpc to make way for other top-level endpoints (e.g. tRPC panel or other API frontends like REST or gRPC).

  If you're using @latticexyz/store-sync packages with an indexer (either createIndexerClient or indexerUrl argument of syncToRecs), then you'll want to update your indexer URL:

   createIndexerClient({
  -  url: "https://indexer.dev.linfra.xyz",
  +  url: "https://indexer.dev.linfra.xyz/trpc",
   });

   syncToRecs({
     ...
  -  indexerUrl: "https://indexer.dev.linfra.xyz",
  +  indexerUrl: "https://indexer.dev.linfra.xyz/trpc",
   });

Minor Changes

• #1240 753bdce4 Thanks @holic! - Store sync logic is now consolidated into a createStoreSync function exported from @latticexyz/store-sync. This simplifies each storage sync strategy to just a simple wrapper around the storage adapter. You can now sync to RECS with syncToRecs or SQLite with syncToSqlite and PostgreSQL support coming soon.

  There are no breaking changes if you were just using syncToRecs from @latticexyz/store-sync or running the sqlite-indexer binary from @latticexyz/store-indexer.

Patch Changes

• #1308 b8a6158d Thanks @holic! - bump viem to 1.6.0

• Updated dependencies [a2588116, 939916bc, b8a6158d, 48c51b52, b8a6158d, b8a6158d, 753bdce4, 5294a7d5, b8a6158d]:

  • @latticexyz/store@2.0.0-next.2
  • @latticexyz/common@2.0.0-next.2
  • @latticexyz/store-sync@2.0.0-next.2
  • @latticexyz/block-logs-stream@2.0.0-next.2

@latticexyz/store-cache@2.0.0-next.2

Patch Changes

• Updated dependencies [a2588116, 939916bc, b8a6158d, 48c51b52, b8a6158d]:
  • @latticexyz/store@2.0.0-next.2
  • @latticexyz/common@2.0.0-next.2
  • @latticexyz/schema-type@2.0.0-next.2
  • @latticexyz/config@2.0.0-next.2