This is to migrate our monorepo's linting and formatting from ESLint & Prettier to Biome.js.

Why:

1. Two in One: Biome comes with 190 lint rules from ESlint, TypeScript ESlint, and other sources with 97% compatibility with Prettier. Biome can be used as a replacement for two.
2. Biome adds new CLI options that enables to format and lint only files that changed (using Git)
3. its rust-based and 10x+ faster than eslint!!!

Biome Impact:

based on local run of biome on our monorepo, it runs the checks 10x faster (from 15.6 seconds down to just 1.6 seconds)

migration plan:

1. Run eslint/biome/migrate-rules codemod and make minor tweaks. (156 files changed
2. run biome to apply the required formatting (609 files changed)
3. fixed the linting issues manually for each part of the platform (cli, vsce, studio, etc.)
4. by now all lintings should work fine, so we enable the linting check for github action.

Codemod Impact:

If we were to manually migrate the Codemod Monorepo alone, we would have to:

• adjust 134 existing package.json files:
  • replace ESLint scripts (1 minute per file);
  • replace ESLint deps (1 minute per file);
• find a corresponding rule for each of the existing ESLint rules (2 minutes per rule);
• replace Prettier configuration (5 minutes)

It would have taken up to a whole day of boring mechanical work to perform the migration manually without performing any additional troubleshooting

Node.js 22 upgrade codemods

Codemod description

Codemods to help automate the Node.js 22 upgrade process according to the release notes here.

Codemod engine

TBD

file extensions to process

TBD

Applicability Criteria

from: [["node.js", "<", "22.0.0"]],

what is the earliest version of the package where the new pattern is introduced?
to: ["node.js", "=", "22.0.0"]

post commands - installing/unsintalling packages

TBD

Codemod arguments

TBD

tags for discovery

["node.js", "migration"]

Codemod source URL

TBD

Additional context or links

• Release notes blog
• Annoucement

Add Tinloof's devs to repo contributors after merging the previous repo to this monorepo.

The issue arises when attempting to authenticate the Codemod extension in Cursor. After successful authentication on the web, the website attempts to redirect using the vscode:// URL scheme. However, the Cursor application does not recognize this URL scheme. A workaround has been found where manually changing the URL scheme to cursor:// allows the redirect to work as expected.

Steps to Replicate

1. Open the Cursor application.
2. Install the Codemod extension within the Cursor application.
3. Click on the 'Sign In' button within the Codemod extension.
4. Authenticate with the required credentials on the web.
5. After successful authentication, the website attempts to redirect using the vscode:// URL scheme.

At this point, the Cursor application fails to recognize the vscode:// URL scheme and thus Codemod cannot sign in.

Codemod description

Build a set of codemods for the breaking changed of the new release
you can use one of the following engines:
jscodeshift, ast-grep, ts-morph, filemod (for file transformation)

Applicability Criteria

• Framework/library: react-native
• From: : v0.73.7
• To: v0.74.0

see https://reactnative.dev/blog/2024/04/22/release-0.74#breaking-changes-1
for before after examples.