Create centralized linting system that can be applied to all MatrixAI repos, regardless of project-specific linting rules

[CDeltakai]

Specification

If we can create a single config bundle that includes all of the rules from MatrixAI codebases, we can greatly streamline the process of setting up linting rules in new repos.

Additional context

Tasks

1. Research into how to implement a bundled config file that can be used to apply rules from other eslint-plugins
2. Create a bundled config file that combines all of the commonly used rules in our repos in a single package

[linear]

ENG-557

[CMCDragonkai]

Old dependencies can be replaced with just 1:

This repo has to be an ESM repo too.

https://github.com/MatrixAI/Zeta-House-Docs/blob/staging/scripts/lint.mjs - make sure it works with the lint.mjs code.

[CMCDragonkai]

ETA on this? This has been worked on for a couple weeks now. It should be merged now.

[CMCDragonkai]

@CDeltakai

[CMCDragonkai]

I've reviewed very quickly the result of this work, and I don't think this is what we want. I'm going to give a better spec so that this actually some real ROI, which right now it does not.

1. Every linting rules in every project includes roughly:
   • eslint
   • shellcheck for shell scripts
   • prettier for markdown
   • clang-format for C/C++
   • nix-format for nix
   • rustfmt for rust
2. This repository shouldn't be exporting an eslint plugin. (It can, but that's not the point of this repo).
3. This repository SHOULD be exporting a lint command. And this single lint command should automatically run linting rules for all relevant projects/directories, and downstream repos can "extend it" to filter out certain directories or do extra things.

To achieve this.

1. Rename this repo to be js-lint. That way it represents the totality of linting for the entire organisation.
2. The package.json should be called @matrixai/lint. See point 1.
3. This needs a bin program specified in package.json that runs the lint command. This command should be located under src/bin/lint.ts. It can look like this:

   "bin": {
     "lint": "dist/bin/lint.js"
   },
   

4. The src/bin/lint.ts needs to follow roughly the same structure of "linting" as this script located in zeta.house: https://github.com/MatrixAI/zeta.house/blob/staging/scripts/lint.mjs
5. This repo's dependencies needs to contain all the relevant eslint dependencies that we use, see zeta.house's package.json for a common set. (Yes I know that PKE has different rules, ignore it for now.)
6. We're going to incrementally apply this to the js-logger.
7. There are some "native" dependencies that work as part of the nix develop shell, which brings in shellcheck and clang-format, nixfmt, rustfmt. These dependencies cannot be part of the package.json, because they are native dependencies. The only dependencies that's possible under package.json is eslint and eslint related libraries and prettier.
8. Since the lint script depends on non-JS packages, and uses things like shellcheck... etc. Then what you need to do is one of the 2 things:
   • Option 1: bundle native dependencies into our npm package
   • Option 2: just "test" for the existence of these commands, and run them optionally IF THEY exist in the environment
   • DO OPTION 2. DO NOT DO OPTION 1. Because OPTION 1 is hacky and npm wasn't designed to distribute native commands. And just is bad vooodoooo..

[CMCDragonkai]

I've just done:

1. Rename this repo to be js-lint. That way it represents the totality of linting for the entire organisation.

The rest is handed to you @CDeltakai.

[CMCDragonkai]

For step 8. As an example https://github.com/MatrixAI/zeta.house/blob/a42d071dcf6813ce5a225b4a699fed67881e6d75/scripts/lint.mjs#L46-L69

You just need to "test" if the program already exists in the shell before doing the rest of the code.

if (commandExists('find') && commandExists('shellcheck')) {
  // ...
}

Ask chatgpt to generate the function for you:

• It must work on linux, macos, windows
• It must be very fast
• It must return true/false
• It must take a string representing the program I want to check
• It must check that the program exists in the current environment

[CMCDragonkai]

Step 9. is to do a release on this repo. Create a 0.0.1 version of this @matrixai/lint.

Step 10. is to create a feature branch in js-logger, and get it working there.

Remember the CI does step 9. You just need to create a "version tag".

[CMCDragonkai]

At step 10. we will remove all eslint and linting programs from that repo. And instead the lint and lintfix scripts will just call lint command coming out of this repo. It is possible to do this because of our nix develop shell.

Or we can even call npx @matrixai/lint or npx @matrixai/lint --fix.