# Migrate to 2.0

> Migration guide for Sui TypeScript SDK 2.0 covering all @mysten packages.

This guide covers the breaking changes across the latest release of all the `@mysten/*` packages.

The primary goal of this release is to support the new GRPC and GraphQL APIs across all the mysten
SDKs. These releases also include removals of deprecated APIs, some renaming for better consistency,
and significant internal refactoring to improve maintainability. Starting with this release, Mysten
packages will now be published as ESM only packages.

## Quick reference

| Package                                                               | Key Changes                                                                              |
| --------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
| [`@mysten/sui`](/sui/migrations/sui-2.0/sui)                          | Client API stabilization, SuiClient removal, BCS schema alignment, transaction executors |
| [`@mysten/dapp-kit`](/sui/migrations/sui-2.0/dapp-kit)                | Complete rewrite with framework-agnostic core                                            |
| [`@mysten/kiosk`](/sui/migrations/sui-2.0/kiosk)                      | Client extension pattern, low-level helpers removed, KioskTransaction pattern            |
| [`@mysten/zksend`](/sui/migrations/sui-2.0/zksend)                    | Client extension pattern                                                                 |
| [`@mysten/suins`](/sui/migrations/sui-2.0/suins)                      | Client extension pattern                                                                 |
| [`@mysten/deepbook-v3`](/sui/migrations/sui-2.0/deepbook-v3)          | Client extension pattern                                                                 |
| [`@mysten/walrus`](/sui/migrations/sui-2.0/walrus)                    | Client extension pattern, requires client instead of RPC URL                             |
| [`@mysten/seal`](/sui/migrations/sui-2.0/seal)                        | Client extension pattern                                                                 |
| [`@mysten/wallet-standard`](/sui/migrations/sui-2.0/wallet-builders)  | Removal of reportTransactionEffects, new core API response format                        |
| [Migrating from JSON-RPC](/sui/migrations/sui-2.0/json-rpc-migration) | Migrate from deprecated JSON-RPC to gRPC and GraphQL                                     |

## Common migration patterns

### ESM migration

All `@mysten/*` packages are now ESM only. If your project does not already use ESM, you will need
to add `"type": "module"` to your `package.json`:

```json
{
	"type": "module"
}
```

If you are using TypeScript with `moduleResolution` `"Node"`, `"Classic"`, or `"Node10"`, you will
need to update your `tsconfig.json` to use `"NodeNext"`, `"Node16"`, or `"Bundler"`:

```json
{
	"compilerOptions": {
		"moduleResolution": "NodeNext",
		"module": "NodeNext"
	}
}
```

This enables proper resolution of the SDK's subpath exports (for example, `@mysten/sui/client`,
`@mysten/sui/transactions`).

If you maintain a library that depends on any of the `@mysten/*` packages, you might also need to
update your library to be ESM only to ensure it works correctly everywhere.

Applications using bundlers and recent Node.js versions (>=22) might still work when using `require`
to load ESM packages, but we recommend migrating to ESM.

**Why ESM only?** Many packages in the ecosystem (specifically critical cryptography dependencies)
are now published as ESM only. Supporting CommonJS has prevented us from using the latest versions
of these dependencies, making our SDKs harder to maintain and risking missing critical security
updates.

### Client migration

The most common change across all SDKs is migrating from `SuiClient` to `SuiJsonRpcClient`:

```diff
- import { SuiClient, getFullnodeUrl } from '@mysten/sui/client';
+ import { SuiJsonRpcClient, getJsonRpcFullnodeUrl } from '@mysten/sui/jsonRpc';

- const client = new SuiClient({ url: getFullnodeUrl('mainnet') });
+ const client = new SuiJsonRpcClient({
+   url: getJsonRpcFullnodeUrl('mainnet'),
+   network: 'mainnet',
+ });
```

We also recommend moving from the deprecated JSON RPC APIs to the new gRPC API as soon as possible:

```diff
- import { SuiJsonRpcClient } from '@mysten/sui/jsonRpc';
+ import { SuiGrpcClient } from '@mysten/sui/grpc';

- const client = new SuiJsonRpcClient({ url, network: 'mainnet' });
+ const client = new SuiGrpcClient({ baseUrl, network: 'mainnet' });
```

The gRPC runs on full nodes so in most cases you should be able to use the same URLs when migrating
to gRPC.

### Network parameter required

All client constructors now require an explicit `network` parameter:

```ts
const client = new SuiJsonRpcClient({
	url: getJsonRpcFullnodeUrl('mainnet'),
	network: 'mainnet', // Required
});

const graphqlClient = new SuiGraphQLClient({
	url: 'https://sui-mainnet.mystenlabs.com/graphql',
	network: 'mainnet', // Required
});

const grpcClient = new SuiGrpcClient({
	baseUrl: 'https://fullnode.mainnet.sui.io:443',
	network: 'mainnet', // Required
});
```

### `ClientWithCoreApi` Interface

Many SDK methods now accept any client implementing `ClientWithCoreApi`, enabling use with JSON-RPC,
GraphQL, or gRPC transports:

```ts

// All of these work with APIs that accept ClientWithCoreApi
const jsonRpcClient = new SuiJsonRpcClient({ url, network: 'mainnet' });
const graphqlClient = new SuiGraphQLClient({ url, network: 'mainnet' });
const grpcClient = new SuiGrpcClient({ baseUrl, network: 'mainnet' });
```

## Package-specific guides

For detailed migration instructions, see the SDK-specific guides:

- **[`@mysten/sui`](/sui/migrations/sui-2.0/sui):** Core SDK changes including client API, BCS
  schemas, transactions, zkLogin, and GraphQL
- **[`@mysten/dapp-kit`](/sui/migrations/sui-2.0/dapp-kit):** Complete migration guide for the new
  dApp kit architecture
- **[`@mysten/kiosk`](/sui/migrations/sui-2.0/kiosk):** Kiosk SDK now exports a client extension,
  low-level helpers removed
- **[`@mysten/zksend`](/sui/migrations/sui-2.0/zksend):** zkSend SDK now exports a client extension
- **[`@mysten/suins`](/sui/migrations/sui-2.0/suins):** SuiNS now exports a client extension
- **[`@mysten/deepbook-v3`](/sui/migrations/sui-2.0/deepbook-v3):** DeepBook DEX now exports a
  client extension
- **[`@mysten/walrus`](/sui/migrations/sui-2.0/walrus):** Walrus storage now exports a client
  extension
- **[`@mysten/seal`](/sui/migrations/sui-2.0/seal):** Seal encryption now exports a client extension

## Transport migration

- **[Migrating from JSON-RPC](/sui/migrations/sui-2.0/json-rpc-migration):** Migrate from the
  deprecated JSON-RPC client to gRPC and GraphQL

## Ecosystem migration guides

For wallet builders and SDK maintainers building on the Sui ecosystem:

- **[Wallet builders](/sui/migrations/sui-2.0/wallet-builders):** Guide for wallet implementations
  adapting to `reportTransactionEffects` removal and new core API response format
- **[SDK maintainers](/sui/migrations/sui-2.0/sdk-maintainers):** Guide for SDK authors migrating to
  `ClientWithCoreApi` and the new transport-agnostic architecture

## Non-existent objects

When migrating from the v1 SDK to the v2 SDK, review any code paths that read objects or dynamic
fields that may not exist.

In v1, methods such as `core.getObject` and `getDynamicField` return `null` when the requested
object or field does not exist. In v2, the same operations throw an exception instead. Applications
that previously relied on `null` checks should be updated to handle exceptions appropriately, either
through try/catch blocks or by validating object existence before attempting to read it.

This behavioral change may require updates to error handling logic to avoid unexpected runtime
failures after migration.