33 stable releases (8 major)

8.1.0 Mar 22, 2024
7.1.1 Jan 19, 2024
7.0.0 Aug 7, 2023
6.2.1 Nov 9, 2022
0.2.3 Dec 18, 2020

#8 in WebAssembly

Download history 4873/week @ 2024-01-03 5450/week @ 2024-01-10 6090/week @ 2024-01-17 6624/week @ 2024-01-24 7305/week @ 2024-01-31 8708/week @ 2024-02-07 7148/week @ 2024-02-14 7031/week @ 2024-02-21 8050/week @ 2024-02-28 8268/week @ 2024-03-06 9571/week @ 2024-03-13 9762/week @ 2024-03-20 8791/week @ 2024-03-27 8555/week @ 2024-04-03 10555/week @ 2024-04-10 8293/week @ 2024-04-17

38,028 downloads per month
Used in 55 crates (34 directly)

MIT license




generate typescript type declarations from rust types


When building a web application in rust, data structures have to be shared between backend and frontend. Using this library, you can easily generate TypeScript bindings to your rust structs & enums so that you can keep your types in one place.

ts-rs might also come in handy when working with webassembly.


ts-rs exposes a single trait, TS. Using a derive macro, you can implement this interface for your types. Then, you can use this trait to obtain the TypeScript bindings. We recommend doing this in your tests. See the example and the docs.

get started

ts-rs = "8.1"
use ts_rs::TS;

struct User {
    user_id: i32,
    first_name: String,
    last_name: String,

When running cargo test, the TypeScript bindings will be exported to the file bindings/User.ts.


  • generate type declarations from rust structs
  • generate union declarations from rust enums
  • inline types
  • flatten structs/types
  • generate necessary imports when exporting to multiple files
  • serde compatibility
  • generic types
  • support for ESM imports

cargo features

Feature Description
serde-compat Enabled by default
See the "serde compatibility" section below for more information.
format Enables formatting of the generated TypeScript bindings.
Currently, this unfortunately adds quite a few dependencies.
no-serde-warnings By default, warnings are printed during build if unsupported serde attributes are encountered.
Enabling this feature silences these warnings.
import-esm When enabled,import statements in the generated file will have the .js extension in the end of the path to conform to the ES Modules spec.
Example: import { MyStruct } from "./my_struct.js"
serde-json-impl Implement TS for types from serde_json
chrono-impl Implement TS for types from chrono
bigdecimal-impl Implement TS for types from bigdecimal
url-impl Implement TS for types from url
uuid-impl Implement TS for types from uuid
bson-uuid-impl Implement TS for types from bson
bytes-impl Implement TS for types from bytes
indexmap-impl Implement TS for types from indexmap
ordered-float-impl Implement TS for types from ordered_float
heapless-impl Implement TS for types from heapless
semver-impl Implement TS for types from semver

If there's a type you're dealing with which doesn't implement TS, use either #[ts(as = "..")] or #[ts(type = "..")], or open a PR.

serde compatability

With the serde-compat feature (enabled by default), serde attributes can be parsed for enums and structs. Supported serde attributes:

  • rename
  • rename-all
  • rename-all-fields
  • tag
  • content
  • untagged
  • skip
  • flatten
  • default

Note: skip_serializing and skip_deserializing are ignored. If you wish to exclude a field from the generated type, but cannot use #[serde(skip)], use #[ts(skip)] instead.

When ts-rs encounters an unsupported serde attribute, a warning is emitted, unless the feature no-serde-warnings is enabled.


Contributions are always welcome! Feel free to open an issue, discuss using GitHub discussions or open a PR. See CONTRIBUTING.md


  • serde compatibility layer
  • documentation
  • use typescript types across files
  • more enum representations
  • generics
  • don't require 'static

License: MIT


~125K SLoC