NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
npm · #4918 most downloaded on npm
Core types and helpers for encoding and decoding byte arrays on Solana
Last release 6 days ago
28 Sep 2026
Ships fairly regularly
a new release about every 8 days
Nearly every release is documented
notes for 39 of 39 stable releases
1 version withdrawn
withdrawn after publishing
3 years old
2267 releases · first in 2023
One column per quarter.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that b
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#374 2fb1fbc Thanks @steveluscher! - The SysvarEpochRewards encoder/decoder no longer produces malformed data
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#379 e143797 Thanks @steveluscher! - The SysvarStakeHistory encoder/decoder no longer produces malformed data
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#409 24a329d Thanks @mcintyre94! - Loosen lifetime constraint on sendAndConfirmTransaction to only require lastValidBlockHeight
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [2fb1fbc, 36a9dee, 41b679c, 24a329d, 41b679c, e143797, 776e18d, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [ca1d4ec, 7e7b2ef, 36a9dee, 41b679c, ca1d4ec]:
#236 ca1d4ec Thanks @steveluscher! - RPC methods that take no parameters no longer rely on having a placeholder NO_CONFIG argument. Removing it will save you from wondering why it exists.
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#433 41b679c Thanks @steveluscher! - Corrected a misspelling of readonlyIndexes in the AddressLookupTable type. This fixes the return type of the getTransaction RPC call.
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [7e7b2ef, 36a9dee, 41b679c, 41b679c, 776e18d, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#433 41b679c Thanks @steveluscher! - Corrected a misspelling of readonlyIndexes in the AddressLookupTable type. This fixes the return type of the getTransaction RPC call.
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [7e7b2ef, 36a9dee, 41b679c, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [7e7b2ef, 36a9dee, 41b679c, 41b679c, 776e18d, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#353 7e7b2ef Thanks @steveluscher! - Removed OPTIONS_OBJECT_POSITION_BY_METHOD, downcastNodeToNumberIfBigint(), applyDefaultCommitment(), getIntegerOverflowNodeVisitor(), getBigIntUpcastVisitor(), and getTreeWalker() from the exports of @solana/rpc-transformer
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#433 41b679c Thanks @steveluscher! - Corrected a misspelling of readonlyIndexes in the AddressLookupTable type. This fixes the return type of the getTransaction RPC call.
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, 776e18d, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#409 24a329d Thanks @mcintyre94! - Loosen lifetime constraint on sendAndConfirmTransaction to only require lastValidBlockHeight
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, 41b679c, 776e18d, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#433 41b679c Thanks @steveluscher! - Deprecated the writableIndices/readableIndices spellings in transaction messages in favour of readonlyIndexes/writableIndexes. This will make this shape compatible with the output of the getTransaction API that uses those spellings for address lookup table data.
#193 776e18d Thanks @mcintyre94! - Strip the TransactionMessageWithDurableNonceLifetime type when prepending instructions to a TransactionMessage
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
Updated dependencies [36a9dee, 41b679c, 41b679c, 776e18d, ca1d4ec]:
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
@solana/* dependency in your project at any given time@solana/* dependencies to v2.1.1 at minimum, even if their minor or patch versions differ.const myAddress = address('1234..5678'); // from @solana/addresses@2.0.0
const myAccount = await fetchEncodedAccount(
// imports @solana/addresses@2.1.0
rpc,
// @ts-expect-error Address types mismatch between installed versions of @solana/addresses
myAddress,
);
#236 ca1d4ec Thanks @steveluscher! - The minimum TypeScript version is now 5.3.3
#473 36a9dee Thanks @steveluscher! - The identity of all branded types has changed in such a way that the types from v2.1.1 will be compatible with any other version going forward, which is not the case for versions v2.1.0 and before.
If you end up with a mix of versions in your project prior to v2.1.1 (eg. @solana/addresses@2.0.0 and @solana/addresses@2.1.0) you may discover that branded types like Address raise a type error, even though they are runtime compatible. Your options are:
Note truncated.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →