Provides the it@M code formatter rules for Prettier as an artifact so that they can be used as a standard configuration for projects using Prettier as formatting tool. Alternatively, this configuration can be used as a base configuration and be extended with your own rules.
This configuration is intended to be used with TypeScript-based projects, but might also work with vanilla JavaScript projects.
- Prettier 3.x.x or higher
- TypeScript 5.2.2 or higher
Information: The configuration might also work with older versions but was not tested.
Some Prettier plugins (like @ianvs/prettier-plugin-sort-imports) need information about the TypeScript version used in your project. this configuration assumes you are using Typescript 5.2.2 in your project. This configuration will be updated regulary to always set the latest minor version of TypeScript.
See the open issues for a full list of proposed features (and known issues).
Install the package as dev dependency via your desired package manager, e.g.
npm install -D @muenchen/prettier-codeformat- Configure Prettier by defining the standard configuration inside
package.json
{
"name": "my-cool-library",
"version": "9000.0.1",
"prettier": "@muenchen/prettier-codeformat"
}- Configure Prettier by defining the standard configuration inside
.prettierrc.json
"@muenchen/prettier-codeformat"Further information can be found on the official Prettier documentation
Information: Overriding the settings of this configuration is currently not possible (opposed to as stated in the Prettier documentation).
To further develop this configuration you need to be able to run the development dependencies for releases with semantic-release on your machine.
This requires at least Node 20.x on your system (and in the GitHub Actions pipeline).
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please open an issue using the provided issue templates, fork the repo and create a pull request. Don't forget to give the project a star! Thanks again!
- Open an issue using the appropriate template (bug report, feature request)
- Fork the Project
- Create your branch
- Commit your changes with commit messages following the convention of Angular
- Push to the branch (
git push origin feature/AmazingFeature) - Open a pull request
More about this in the CODE_OF_CONDUCT file.
Distributed under the MIT License. See LICENSE file for more information.
it@M - [email protected]