kimamula / ts-toolbelt Goto Github PK

👷 Higher type safety for TypeScript
Explore the docs »

🎮 View Demo · 🐞 Report Bug · 🍩 Request Feature . 🤔 Ask Questions

• 📜 About
• 🍩 Features
• 🏁 Getting started
• 📖 Documentation
• 👌 Good to know
• 🎁 Contributing
• 👏 Sponsoring issues
• 💉 Running tests
• 🔧 Compatibility
• 🔮 What's next
• 🙏 Acknowledgments

ts-toolbelt is a collection of types that makes TypeScript even safer. It's goal is to improve type correctness while adding a whole new set of features to TypeScript.

It uses the type system itself for TypeScript to compute more complex types. In other words, its API exposes types that trade CPU & RAM for higher type safety.

ts-toolbelt completes TypeScript with a collection of more than 150 tested types.

• This package aims to be the home of all utility types
• Keep reasonable performance, so it will not bloat TS
• Computed types are always readable, like if you typed it
• Software that's more type-safe, flexible & more robust
• Bring a whole new set of extra features to TypeScript
• Types can be combined together to create new ones!

Here's some of the most useful features:

• Merge two types together
• Update the field of a type
• Make some fields optional
• Change a type at any depth!
• Concat two tuples together
• Get the last item of a tuple
• ... and so much more

If you don't find the type you are looking for, you are welcome to open a feature request!

This is important, the lowest TypeScript version that is supported is 3.5

npm install typescript@^3.5.0 --save

npm install ts-toolbelt --save

import {A, B, C, F, I, N, O, S, T, U} from 'ts-toolbelt'
// Wonder what these letters mean? Check the docs below

// Merge two `object` together
type merge = O.Merge<{name: string}, {age?: number}>

The project is organized around TypeScript's main concepts:

There are many ways to import the types into your project:

• Explicit

  import {Any, Boolean, Class, Function, Iteration, Number, Object, String, Tuple, Union} from 'ts-toolbelt'

• Compact

  import {A, B, C, F, I, N, O, S, T, U} from 'ts-toolbelt'

• Portable

  import tb from 'ts-toolbelt'

If you're interested to learn how the internals work, this tutorial will get you on track to start writing your own types.

In this wiki, you'll find some extra resources for your learning & understanding.

It is incremental and it will be completed on demand, you can ask for this below.

Are you missing something? Participate to the open-wiki by posting your questions right here.

Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated. There are many ways to contribute to the project:

• Help the community with answers on Gitter
• Reporting bugs or requesting new features

• Improving existing documentation
• Adding new types to the collection

1. Read the tutorial
2. Fork the project
3. Clone your fork
4. Create a pr/feature branch

   git checkout -b pr/CoolFeature

5. Commit your changes

   git commit -m 'Added this CoolFeature'

6. Run the tests
7. Commit your changes

   git push origin pr/CoolFeature

8. Open a pull request

Sponsored issues have higher priority over non-critical issues.

You can either request a new feature or a bug fix then fund it.

The money will be transparently split with an issue's assignees.

To run the lint & type tests, simply run:

npm test

Want to test your own types? Let's get started:

import {A, B, C, F, I, N, O, S, T, U, Test} from 'ts-toolbelt'

const {checks, check} = Test

checks([
    check<N.Plus<'1', '30'>,    '31',  Test.Pass>(),
    check<N.Plus<'5', '-3'>,    '2',   Test.Pass>(),
])

Place it in a file that won't be executed, it's just for TypeScript to test types

The project is maintained to adapt to the constant changes of TypeScript:

Major version numbers will upgrade whenever TypeScript had breaking changes (it happened that TS had breaking changes on minor versions). Otherwise, the release versions will naturally follow semantic versioning.

• Automated performance tests

  # performance is checked manually with 
  npx tsc --noEmit --extendedDiagnostics

• Improve with user feedback
• Need to write the examples

Many, many thanks to all the contributors and:

• André Staltz
• Joe Calzaretta
• Matt McCutchen