insane VS prettier

Vue does not have as much support for Vue as there is for React. Examples are markdown-it, Remark.js, marked.js. But hopefully in the future, there should be more support, and after much research, I picked marked.js because it has the most stars and has zero vulnerability. Marked does not sanitize (meaning it does not secure HTML documents from attacks like cross-site scripting (XSS) ) marked output HTML as that feature is deprecated and has vulnerability but however, it supports the use of other libraries to secure output HTML such as DOMPurify (recommended), sanitize-html or insane.

In the dynamic world of full-stack development, incorporating linting and formatting tools such as ESLint and Prettier, along with your TypeScript projects, is essential. This integration is particularly important in team settings to ensure code uniformity in syntax and style. Additionally, these tools play a vital role in early detection of errors and bugs. In this article, we'll explore how these tools automate the coding process to produce clean, consistent, and production-ready code.

I have a PR fixing that: https://github.com/prettier/prettier/pull/15209

Just needs another maintainer's stamp.

Some things overlooked in that blog post for others to take into consideration:

- eslint only works on javascript + typescript (eslint + typescript needs _more_ configuration than eslint + prettier), while prettier works on https://github.com/prettier/prettier/blob/03ebc7869dc9e8f2fc...

- eslint + prettier doesn't need lots of configuration from the user. You add eslint-plugin-prettier and say `"extends": ["plugin:prettier/recommended"]`

prettier. A code formatter and linter for code formatting. It ensures that all our files have a consistent appearance.

One of the greatest things about a monorepo is that you can centralise a lot of tooling configuration. For example, chuck a .prettierrc in the root of your monorepo and you'll never have arguments about code style again. Put a few base tsconfigs in the there to extend, and suddenly TypeScript behaves with beautiful consistency across all your packages. Add formatting, linting and husky as dependencies in the root of your workspace and you no longer need to work through upgrading everything individually when a new version comes out.

To get all your code into a consistent format the next step is to run a formatter. I recommend black, the well-known uncompromising code formatter, which is the most popular choice. Alternatives to black are autoflake, prettier and yapf, if you do not agree with blacks constraints.

The following interview of my open source professor, with the early developers of prettier, does a great job at highlighting the importance of such formatters, and how blessed we should feel to have them at our disposal.

This week I had to set up and configure Prettier, ESLint, Husky & lint-staged dependencies to my codebase for better code formatting and linting and VSCode integration with prettier, eslint and pre-commit hooks using husky and lint-staged for achieving automation for linting and formatting.

Code Formatting with Prettier: The code is automatically formatted with Prettier, ensuring consistency in writing style.

Prettier