Skip to content

Opinionated and advisable packages to configure tools to develop a Typescript project

License

Notifications You must be signed in to change notification settings

escemi-tech/ts-dev-tools

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Homepage

npm Continuous integration Code coverage License: MIT PRs Welcome Sponsor GitHub stars


Welcome to ts-dev-tools ๐Ÿ› ๏ธ

Opinionated and advisable packages to configure tools to develop a Typescript project


Why ts-dev-tools ?

1. Aims to provide a first-class developper experience

Install ts-dev-tools and your project is dev ready, no more installation or setup, it just works

2. A fine tuned collection of tools and configuration ready for a realworld project

Within the dozen of existing packages, ts-dev-tools uses a short list of consistent libraries and their recommanded configuration. ts-dev-tools is used by various real world projects to be run in production, so its toolset is effective and meets industry standards.

3. Stable and secure

For every changes and dependency update, ts-dev-tools is:

3. One package to rule them all, one dependency to keep up to date

Dependencies are updated all weeks in order to keep dev tools up to date agains security issues and to give access to the latest available feature.

Using ts-dev-tools you should just have to update it and you'll have all the dev dependencies used by ts-dev-tools, up to date !

Usage

1. Choose the plugin that fits with you need

Name Description
@ts-dev-tools/core Common Typescript tools (Eslint and prettier, lint-staged and pretty-quick)
@ts-dev-tools/react Dev tools for a for ReactJS project

2. Install

Example with plugin @ts-dev-tools/core, replace @ts-dev-tools/core by the plugin you want to use

npm install --include=dev @ts-dev-tools/core

Or

yarn add --dev @ts-dev-tools/core

3. Enable ts-dev-tools

npx ts-dev-tools install

Or

yarn ts-dev-tools install

โš ๏ธ If your package is not private and you're publishing it on a registry like npmjs.com, you need to disable postinstall script using pinst. Otherwise, postinstall will run when someone installs your package and result in an error.


Author

๐Ÿ‘ค Escemi contact@escemi.com

๐Ÿค Contributing

Contributions, issues and feature requests are welcome!
Feel free to check issues page. You can also take a look at the contributing guide and Contributor Code of Conduct.

Show your support

Give a โญ๏ธ if this project helped you!

๐Ÿ“ License

This project is MIT licensed.