ESLint VS prettier

There are two tools for that: Prettier and ESLint.

ESLint: Also static analysis

For the linter, I chose ESLINT. I chose it because ESLINT is a very common linter for javascript code, and there's a lot of useful guides on setting it up. Here's the link for ESLINT: https://eslint.org/

ESLint is another VSCode extension and/or npm module that can be used to check for lint warnings and errors live while programming, or with a simple command run. I chose ESLint as I have chosen to have it in react projects in the past and figured it would be easy to start with. The documentation can be found here

ESLint

To catch common coding issues and enforce best practices, I chose ESLint as the linter for the Barrierless project. ESLint is highly configurable, and it integrates well with JavaScript projects, identifying potential errors, bad practices, and non-standard code.

For my linter I chose ESLint. Similar to Prettier I have never set it up. The docs for ESLint was kinda hard to follow. But similar to prettier I went to the docs then to the get started. Followed and ran the scripts to install it by running npm init @eslint/config@latest. After I ran

For linting, my go-to is usually ESLint. Unlike formatting, which is meant to keep your code clean and readable, linting helps detect issues in your code, such as unused variables, attempts to change an immutable variable, and many more. ESLint is my go-to because I always use Airbnb's ESLint Configurations in my projects. ESLint allows you to set many rules for your source code, such as using a specific naming convention, forbidding vanilla for-loops, or prefix and postfix operators, restricting single exports in a file to export default, and many more.

Consider using a linter: A linter can help you catch potential errors and enforce coding standards in your project. Popular linters for JavaScript include ESLint and Prettier.

ESLint: Finds JavaScript problems

VS Code is my preferred IDE and I recommend it to my team. Additionally, we use Prettier to enforce consistent, clean code style across our projects.

There are two tools for that: Prettier and ESLint.

Prettier: Checking formatting

For the code formatter, I chose prettier. This is because my project uses javascript as its main language, and I felt like it would be a simple setup. Here's the link for prettier: https://prettier.io/

Prettier formatter is a VSCode extension and/or npm module that can be used to format code in a nice looking way with a simple command or the click of a button. I chose prettier as I had been using it already to format my documents in VSCode for quite a while now, and on my old PC had it set up for formatting on save from an older project in last year's cloud computing class. The documentation can be found here

Prettier

Since Barrierless is primarily built in JavaScript, I decided to use Prettier as the project’s source code formatter. Prettier is a popular choice in the JavaScript community, known for enforcing a consistent code style automatically. With Prettier, formatting rules are predefined and eliminate the need for contributors to focus on stylistic details, allowing them to focus on the code logic itself.

For my source code formatter, I choose Pretter. It is very popular and I have seen it other projects but I never had to set it up from scratch so I wanted to do that. First thing I did was go to thier docs and followed their install instructions. I also updated the .prettierignore so that I could exclude the files and directories I don't want to be formatted. Then I ran

For formatting, my go-to is always the beloved Prettier package/extension! This was introduced to me first in the Cloud Computing for Developers course I took with Professor Humphrey last year.