NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
pub.dev
pub.dev
Client library needed for the code generated by the arri server library.
Latest stable
0.85.0
Last release 1 months ago
03 Oct 2026
Release timing varies
gaps range from 2 weeks to 6 months
Most releases are documented
notes for 52 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
3 years old
223 releases · first in 2023
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
[ts-codegen] fix regression where generated enum validator type name is incorrect by @joshmossas in https://github.com/modiimedia/arri/pull/200
Full Changelog: https://github.com/modiimedia/arri/compare/v0.84.0...v0.84.1
[ts-codegen] the typescriptClient generator now accepts an optional features object to enable and disable some of the generated helper functions
[ts-codegen] the typescriptClient generator now accepts an optional features object to enable and disable some of the generated helper functions
export default defineConfig({
generators: [
generators.typescriptClient({
features: {
validateFn: true, // output a "validate" helper fn for every type (default: false)
cloneFn: true, // output a "clone" helper fn for every type that does a deep clone (default: false)
validatorObj: true, // output a validator object for every type that is prefixed with $$ (default: true)
}
// rest of config
})
]
})
[ts-codegen] BREAKING: the typescriptClient generator no longer outputs the validate helper fn by default. You must enable it in the arri config
[ts-codegen] The outputted typescript code is now much more treeshakable.
import { MyTypeFromJsonString, MyTypeToJsonString, MyTypeValidate } from './my-client.g';
const result = MyTypeFromJsonString('{}');
MyTypeToJsonString(result);
MyTypeValidate(result);
// the old way is still available but it is less tree-shakable
// this will cause FromJson, ToJson, New, and any other helper fns for this type to be imported
import { $$MyType } from './my-client.g';
const result = $$MyType.fromJsonString('{}');
Full Changelog: https://github.com/modiimedia/arri/compare/v0.83.1...v0.84.0
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Full Changelog: https://github.com/modiimedia/arri/compare/v0.83.0...v0.83.1
Full Changelog: https://github.com/modiimedia/arri/compare/v0.83.0...v0.83.1
dart client: SSE partial character parsing bugfix by @joshmossas in https://github.com/modiimedia/arri/pull/197
Full Changelog: https://github.com/modiimedia/arri/compare/v0.82.0...v0.83.0
I marked this as a breaking change just in case, however nobody should be broken by these changes.
I marked this as a breaking change just in case, however nobody should be broken by these changes.
For enums ts-codegen will now also output a static object with all of the possible values. Example:
// before
export type MyEnum = (typeof $$MyEnumValues)[number];
const $$MyEnumValues = ["foo", "bar", "baz"];
// after
export type MyEnum = "foo" | "bar" | "baz";
export const MyEnum = {
Foo: "foo",
Bar: "bar",
Baz: "baz",
} as const;
const $$MyEnumValues = ["foo", "bar", "baz"];
This allows users to access enum variants like so if they so choose:
console.log(MyEnum.Foo)
The actual type remains a string union so consumers aren't affected.
The generated typescript code now outputs 10%-25% less lines of code on average.
Full Changelog: https://github.com/modiimedia/arri/compare/v0.81.3...v0.82.0
Nothing published for this version
feature: add annotation to ignore clippy lints in rust codegen output by @joshmossas in https://github.com/modiimedia/arri/pull/192
Full Changelog: https://github.com/modiimedia/arri/compare/v0.81.2...v0.81.3
[@arrirpc/schema] feat: add a.toJsonSchema() function
a.toJsonSchema() functionarri export json-schema ./app-definition.json
Full Changelog: https://github.com/modiimedia/arri/compare/v0.81.1...v0.81.2
fix(rust-codegen): emit nested service struct definitions by @michael-dm in https://github.com/modiimedia/arri/pull/188
Full Changelog: https://github.com/modiimedia/arri/compare/v0.81.0...v0.81.1
BREAKING [ts-codegen] new Date(0) is now the fallback value for timestamps instead of new Date()
new Date(0) is now the fallback value for timestamps instead of new Date()DateTime(0) is now the fallback value for timestamps instead of DateTime.now()Full Changelog: https://github.com/modiimedia/arri/compare/v0.80.3...v0.81.0
fix build issues on windows when running arri dev and arri build. Fixes are in place for both the go server plugin and ts server plugin
arri dev and arri build. Fixes are in place for both the go server plugin and ts server plugintimeout parameter to generated clients that accepts a Duration. This parameter is used to set a default timeout duration for http requestsheartbeatIntervalMultiplier parameter to generated clients. This is used when setting heartbeat timeouts for server sent events.Full Changelog: https://github.com/modiimedia/arri/compare/v0.80.2...v0.80.3
remove unnecessary logs + add lint rules to prevent unnecessary logs … by @joshmossas in https://github.com/modiimedia/arri/pull/176
Full Changelog: https://github.com/modiimedia/arri/compare/v0.80.1...v0.80.2
feature: add support for heartbeatTimeoutMultiplier to generated dart clients by @joshmossas in https://github.com/modiimedia/arri/pull/175
heartbeatTimeoutMultiplier to generated dart clients by @joshmossas in https://github.com/modiimedia/arri/pull/175Full Changelog: https://github.com/modiimedia/arri/compare/v0.80.0...v0.80.1
This release adds built-in heartbeat support for the Typescript server and Go server. It also adds built-in heartbeat detection for the Typescript and
This release adds built-in heartbeat support for the Typescript server and Go server. It also adds built-in heartbeat detection for the Typescript and Dart clients (further client support will be added in subsequent releases). All event stream rpcs now automatically emit heartbeat messages at regular intervals (customizable)
This also lays some of the groundwork for support of other transports such as Websockets, which will also be making use of automatic heartbeat detection to detect dropped connections. (We aren't there yet but it's one step in that direction :wink: )
SseOptions now includes a heartbeatTimeoutMultipler options which is used internally when setting the heartbeat timeoutsIf you have any event stream rpcs registered using @arrirpc/server all of the http routes for those procedures will be changed from "get" to "post". If want to prevent from breaking existing clients you can manually change the http method to "get". If you don't care about breaking past clients then you can just ignore.
defineEventStreamRpc({
method: "get", // add this line
...
})
All previous http methods are still supported. The only thing that has changed is the default behavior. All procedures now register routes as a "post" request as default unless specified otherwise. (This also makes behavior consistent between the TS server and Go server).
Full Changelog: https://github.com/modiimedia/arri/compare/v0.79.1...v0.80.0
chore: update javascript libs + add benchmarks for Zod/v4 by @joshmossas in https://github.com/modiimedia/arri/pull/172
Full Changelog: https://github.com/modiimedia/arri/compare/v0.79.0...v0.79.1
This conforms more to user expectation however it is a breaking change
Because this contains changes to the internal schemas, all server implementations and code generators have been affected. The external interfaces haven't necessarily changed, but you will need to upgrade all your Arri dependencies together (Ex: your server and client libraries both must be upgraded to v0.79.0). You can use npx arri use latest at the root of your repo to simplify this process.
The following modifications have been made to the internal Arri Type Definition and Arri App Definition specifications:
nullable keyword has been renamed to isNullablestrict keyword has been renamed to isStrictdeprecatedNote to Arri Type Definition metadatadeprecatedNote to Arri App Definition proceduresThis change has been made to ensure all boolean values in the Arri specifications conform to the same naming convention (ex: isDeprecated, isEventStream, etc). The addition of the deprecatedNote keyword lays the groundwork to enable Arri generators to include specific deprecation messages for types, fields, and procedures.
The schemaVersion value has been incremented to v0.0.8
a.optional() now makes object keys optional in TS rather than just T | undefined
a.undefinable() has been added. It behaves the way that a.optional() used to behave. (It makes a field T | undefined but the key must still be present when initializing the object in TS)strict option for object schemas has been marked as deprecatedisStrict has been added as an option for object schemasa.optional makes object keys optional + add a.undefinable schema which mimicks old behavior of a.optional() by @joshmossas in https://github.com/modiimedia/arri/pull/170Full Changelog: https://github.com/modiimedia/arri/compare/v0.78.0...v0.79.0
[ts-client] feature: add support for automatic retry, timeouts, and request hooks in typescript clients by @joshmossas in https://github.com/modiimedi
ArriRequestOptions to ArriRequestConfigFull Changelog: https://github.com/modiimedia/arri/compare/v0.77.1...v0.78.0
[cli] bugfix: ensure that dynamic imports use windows compliant file paths on windows by @joshmossas in https://github.com/modiimedia/arri/pull/164
arri dev or arri build would crash on windowsFull Changelog: https://github.com/modiimedia/arri/compare/v0.77.0...v0.77.1
This release adds the ability to define a root service when generating clients. This makes it easier to publish more narrowly scoped RPC client from t
This release adds the ability to define a root service when generating clients. This makes it easier to publish more narrowly scoped RPC client from the same app. For example consider a service with the following procedures:
Setting the rootService to users would generate a client that only has the following procedures: [getUser, updateUser]. While setting the rootService to posts would generate a client that only has [createPost, updatePost, deletePost].
Some potential use cases:
v1 or v2 and then publish a ClientV1 and ClientV2admin and public procedures with publicimport { defineConfig, generators } from 'arri';
export default defineConfig({
generators: [
generators.typescriptClient({
clientName: 'ClientV1',
rootService: 'v1', // only include procedures from the `v1` service
outputFile: '<some-output-path>',
}),
generators.typescriptClient({
clientName: 'ClientV2',
rootService: 'v2', // only include procedures from the `v2` service
outputFile: '<some-output-path>',
}),
],
})
rootService optionstart event upon successful connectiononRequest, onBeforeResponse, onAfterResponse, and onError) no longer receive a pointer to *http.Request as their first parameter. Instead this can be accessed from the RpcEvent like so event.Request()rootService optionv1.8.0v3.1.1rootService optionrootService optionstart event upon successful connectionprefer-modular-imports lint rule for users that want to enforce keeping as small a bundle size as possiblerootService optionv1.25.2message eventrootService in code generators [ts, rust, dart, kotlin, swift] by @joshmossas in https://github.com/modiimedia/arri/pull/159arri/prefer-modular-imports eslint rule to @arrirpc/eslint-plugin by @joshmossas in https://github.com/modiimedia/arri/pull/160Full Changelog: https://github.com/modiimedia/arri/compare/v0.76.4...v0.77.0
[go-server]: fix bug where list of validation returned by DecodeJSON is always empty
DecodeJSON is always emptyDecodeJSON result by @joshmossas in https://github.com/modiimedia/arri/pull/154Full Changelog: https://github.com/modiimedia/arri/compare/v0.76.3...v0.76.4
This update allows you to optionally passing in a custom implementation of fetch to the generated Arri TS clients. The main goal of this patch is to p
This update allows you to optionally passing in a custom implementation of fetch to the generated Arri TS clients. The main goal of this patch is to provide escape hatches for environments that do not natively support fetch or in environments where fetch is not spec compliant and thus produces unexpected results. (i.e. React Native and text streaming)
Full Changelog: https://github.com/modiimedia/arri/compare/v0.76.0...v0.76.3
Nothing published for this version
Since the majority of people do not use the properties available in .compiledCode this will not be a breaking change for most. If you need to access t…
Full Changelog: https://github.com/modiimedia/arri/compare/v0.75.0...v0.76.0
When using compiled validators the .compiledCode property is now undefined by default. From my tests this reduces unnecessary memory usage by 65% for small schemas and by 73% for larger schemas. Results will vary from schema to schema but overall there should be a large reduction in memory allocations. Basically now the large function body strings are no longer being stored by default so we save in memory usage.
const User = a.object("User", {
id: a.string(),
name: a.string(),
email: a.nullable(a.string()),
});
const $$User = a.compile(User);
$$User.compiledCode // this is `undefined`
Since the majority of people do not use the properties available in .compiledCode this will not be a breaking change for most. If you need to access the generated function bodies for use in something like code-generation, you now need to explicitly enable the feature like so:
const User = a.object("User", {
id: a.string(),
name: a.string(),
email: a.nullable(a.string()),
});
const $$User = a.compile(User, true) // passing true as the second parameter makes `.compiledCode` available
$$User.compiledCode // this is no longer undefined
// so we can access the generated function bodies
console.log($$User.compiledCode.validate)
console.log($$User.compiledCode.parse)
console.log($$User.compiledCode.serialize)
Nothing published for this version
Nothing published for this version
feature: empty object support for arri generators by @joshmossas in https://github.com/modiimedia/arri/pull/149
async-http-client to v1.25.1esbuild to v0.25.0Full Changelog: https://github.com/modiimedia/arri/compare/v0.74.1...v0.75.0
__dart-codegen__ - bugfix - prefix enums that use reserved keywords such as default by @joshmossas in https://github.com/modiimedia/arri/pull/147
default by @joshmossas in https://github.com/modiimedia/arri/pull/147Full Changelog: https://github.com/modiimedia/arri/compare/v0.74.0...v0.74.1
bugfix: fix failing kotlin integration tests against go server by @joshmossas in https://github.com/modiimedia/arri/pull/142
Full Changelog: https://github.com/modiimedia/arri/compare/v0.73.0...v0.74.0
Since we are pre-1.0 I thought now was a good time to do a major refactor to change the default behavior of the TS schema validation library. Now all parsing and serialization functions will never not throw errors by default. Instead they return a Result<T>.
parse, coerce, and serialize no longer throw a ValidationError they instead return a Result<T>parseSafe and coerceSafe have been removed as not throwing is now the default behaviorparseUnsafe, coerceUnsafe, and serializeUnsafe have been added.ValidationError has been renamed to ValidationExceptiona.compile() now also compiles a highly optimized coerce function. When running on my Macbook the compile version of coerce is 25x faster than the non-compiled versions.<img width="1455" alt="image" src="https://github.com/user-attachments/assets/db892c3d-dc42-44df-a0f4-50f5a6a978ba" />
coerce() when parsing URL query params.async-http-client to version 1.24.2bugfix: fix codgen bugs when using typePrefix option in dart, kotlin, swift, and rust by @joshmossas in https://github.com/modiimedia/arri/pull/137
typePrefix option in dart, kotlin, swift, and rust by @joshmossas in https://github.com/modiimedia/arri/pull/137Full Changelog: https://github.com/modiimedia/arri/compare/v0.72.0...v0.73.0
modelPrefix option has been renamed to typePrefix for consistency with other client generatorstypePrefix option sometimes results in invalid Dart codetypePrefix option sometimes results in invalid Rust codetypePrefix options results in invalid Swift codepathe dependency when running arri buildmake arri use command stricter on versions for package.json and pubspec.yaml. by @leccles1 in https://github.com/modiimedia/arri/pull/133
Upgrade with arri use latest
arri use command stricter on versions for package.json and pubspec.yaml. by @leccles1 in https://github.com/modiimedia/arri/pull/133@arrirpc/typebox-adapter fix type inference issues by @joshmossas in https://github.com/modiimedia/arri/pull/131modelPrefix option by @joshmossas in https://github.com/modiimedia/arri/pull/134Full Changelog: https://github.com/modiimedia/arri/compare/v0.71.1...v0.72.0
Fix bug where compiled validators don't properly pass errors to standard-schema
Full Changelog: https://github.com/modiimedia/arri/compare/v0.71.0...v0.71.1
Feature: add support for standard-schema by @joshmossas in https://github.com/modiimedia/arri/pull/130
Full Changelog: https://github.com/modiimedia/arri/compare/v0.70.1...v0.71.0
json-schema-to-jtd package has been deprecated and replaced with json-schema-to-atd
If a particular language isn't mentioned then no change occurred.
EncodeJSON now accept EncodingOptions as one of it's parametersDecodeJSON now accepts EncodingOptions as one of it's parametersFromUrlQuery has been renamed to DecodeQueryParamsFromUrlQuery now accepts EncodingOptions as one of it's parametersContext interface has been renamed to Event to prevent confusion with context from the STDEncodeJSON in the ArriModel interface now accepts EncodingOptions as its parameterLen() method has been added to OrderedMapEntries() method has been added to OrderedMapKeys() method has been added to OrderedMapjson-schema-to-jtd package has been deprecated and replaced with json-schema-to-atd@arrirpc/jtd-utils package has been deprecated and replaced with @arrirpc/type-defsjson-schema-to-atd now supports converting "string" with "date-time" format to timestamp typelanguages/ts for consistencyFull Changelog: https://github.com/modiimedia/arri/compare/v0.69.2...v0.70.1
feature: add support for dictionary types when converting from JSON schema to ATD by @joshmossas in https://github.com/modiimedia/arri/pull/120
Full Changelog: https://github.com/modiimedia/arri/compare/v0.69.1...v0.69.2
[arri use] bugfix: await all pending go mod file update tasks by @joshmossas in https://github.com/modiimedia/arri/pull/119
Full Changelog: https://github.com/modiimedia/arri/compare/v0.69.0...v0.69.1
feature: golang - expose ArriModel interface publicly by @joshmossas in https://github.com/modiimedia/arri/pull/118
ArriModel is now exposed publiclyYou can now implement the ArriModel interface to tell Arri how a particular struct should be serialized, deserialized, and represented as an Arri Type Definition.
This release also includes an IsArriModel helper function which can be used to test whether a particular struct implements the ArriModel interface
Full Changelog: https://github.com/modiimedia/arri/compare/v0.68.0...v0.69.0
chore: add integration tests for serializing transformed keys by @joshmossas in https://github.com/modiimedia/arri/pull/115
Full Changelog: https://github.com/modiimedia/arri/compare/v0.67.0...v0.68.0
Bugfix: optional types should respect original json key during serialization by @joshmossas in https://github.com/modiimedia/arri/pull/114
Full Changelog: https://github.com/modiimedia/arri/compare/v0.66.0...v0.67.0
Refactor: change schema for Generator used in generator plugins
Generator used in generator pluginsGenerator type has changed from
export interface Generator<TOptions extends Record<string, any> | undefined> {
generator: (def: AppDefinition, isDevServer?: boolean) => any;
options: TOptions;
}
To
export interface Generator<TOptions extends Record<string, any> | undefined> {
// this property has been renamed
run: (def: AppDefinition, isDevServer?: boolean) => any;
options: TOptions;
}
All future generator plugins using 0.66.0 or later must adjust to match this new interface.
Full Changelog: https://github.com/modiimedia/arri/compare/v0.65.2...v0.66.0
Full Changelog: https://github.com/modiimedia/arri/compare/v0.65.1...v0.65.2
Full Changelog: https://github.com/modiimedia/arri/compare/v0.65.1...v0.65.2
remove unnecessary log from init command by @joshmossas in https://github.com/modiimedia/arri/pull/109
Full Changelog: https://github.com/modiimedia/arri/compare/v0.65.0...v0.65.1
Bugfix: go server validations should error with empty body by @joshmossas in https://github.com/modiimedia/arri/pull/107
arri init now supports scaffolding a go projectFull Changelog: https://github.com/modiimedia/arri/compare/v0.63.4...v0.65.0
Nothing published for this version
chore: update ts libs by @joshmossas in https://github.com/modiimedia/arri/pull/105
This release marks conpletion of the first version of the Arri Go server implementation. Some additional modifications must be finalized to make it usable for external applications, so keep an eye open for upcoming releases.
Documentation on the go server can be found in the Readme.
Full Changelog: https://github.com/modiimedia/arri/compare/v0.63.2...v0.63.3
chore: update TS dependencies by @joshmossas in https://github.com/modiimedia/arri/pull/101
Full Changelog: https://github.com/modiimedia/arri/compare/v0.63.1...v0.63.2
Full Changelog: https://github.com/modiimedia/arri/compare/v0.63.0...v0.63.1
Full Changelog: https://github.com/modiimedia/arri/compare/v0.63.0...v0.63.1
bugfix: [dart-codegen] ensure client version is passed down to nested services by @joshmossas in https://github.com/modiimedia/arri/pull/100
Full Changelog: https://github.com/modiimedia/arri/compare/v0.62.0...v0.63.0
chore: update TS and Swift dependencies by @joshmossas in https://github.com/modiimedia/arri/pull/99
ts-server in preparation for major API changesFull Changelog: https://github.com/modiimedia/arri/compare/v0.61.1...v0.62.0
fix bug where int64 and uint64 values were not being serialized properly when they were values of map/dictionary in the generated Kotlin client code
Full Changelog: https://github.com/modiimedia/arri/compare/v0.61.0...v0.61.1
bugfix: support \r and \r\n line separators in Dart sse procedures by @joshmossas in https://github.com/modiimedia/arri/pull/93
\r and \r\n line separators in Dart sse procedures by @joshmossas in https://github.com/modiimedia/arri/pull/93\r and \r\n line separators in Kotlin sse procedures by @joshmossas in https://github.com/modiimedia/arri/pull/94maxBackoffTime as a parameter to Kotlin sse proceduresJob instance. (You can still wrap them in a Job for similar functionality.)modelPrefix to typePrefix in the the Kotlin code generatorFull Changelog: https://github.com/modiimedia/arri/compare/v0.60.3...v0.61.0
bugfix: fix broken swift builds on macOS by @joshmossas in https://github.com/modiimedia/arri/pull/89
Full Changelog: https://github.com/modiimedia/arri/compare/v0.60.2...v0.60.3
feature: [swift] add maxBodyBytes parameter to allow for adjusting the maximum bytes a response body can take up by @joshmossas in https://github.com/
maxBodyBytes parameter to allow for adjusting the maximum bytes a response body can take up by @joshmossas in https://github.com/modiimedia/arri/pull/86Full Changelog: https://github.com/modiimedia/arri/compare/v0.60.1...v0.60.2
Feature: swift client generation by @joshmossas in https://github.com/modiimedia/arri/pull/63
Full Changelog: https://github.com/modiimedia/arri/compare/v0.59.0...v0.60.1
This release introducing the initial version of the Arri Swift Client. For details on how to use it check out the docs
Nothing published for this version
The Typescript server has been migrated to this system to ensure and consistent workflow between languages, so this is a breaking change.
The server plugin system is how we will enable arri to know about how to run different kinds of servers and where to access app definitions to run the client generations.
Server plugins get registered in the arri config file which will override the behaviors of arri build and arri dev in the CLI. A guide on creating a server plugin has also been added to the server implementation guide.
The Typescript server has been migrated to this system to ensure and consistent workflow between languages, so this is a breaking change.
Move TS server options into the tsServer plugin. Basically any property that isn't generators is a TS server specific option.
/////// before ///////
import { defineConfig } from 'arri';
export default defineConfig({
entry: "app.ts",
port: 3000,
generators: [....]
});
/////// after ///////
import { defineConfig, servers } from 'arri';
export default defineConfig({
server: servers.tsServer({
entry: "app.ts",
port: 3000,
}),
generators: [....]
});
Nothing published for this version
No changes
No changes
No changes
No changes
Nothing published for this version
One column per quarter.