Update Node.js version, editor settings, jest, and linting configurations

[kamiazya]

This pull request includes the following changes:

• Update Node.js version and use lockfile on yarn install

• Update editor.codeActionsOnSave value in settings.json

• Migrate jest to vitest

• Remove Prettier and ESLint configurations, switch to Biome for linting and formatting

Summary by CodeRabbit

• Chores
  • Updated the GitHub Actions workflow to use Node.js version 20.x and improved caching with Yarn.
• Refactor
  • Enhanced code consistency in various files by standardizing the use of double quotes for string literals and import statements.
  • Transitioned from jest to vitest for testing, including updates to test descriptions and mocking methods.
• Style
  • Adjusted VS Code settings for more explicit code action triggers on save.

[coderabbitai]

Walkthrough

The overall changes involve updates and refinements across various configuration and source files within a project. Key updates include upgrading Node.js version for workflow actions, enhancing caching strategy with Yarn, enforcing stricter linting conditions, and adopting consistent quoting practices in TypeScript code. Additionally, the test suite transitions to a new testing framework with updated syntax and conventions for mocking and assertions.

Changes

Files	Change Summary
.github/.../workflow.yaml	Updated node-version to 20.x, added cache: yarn, modified yarn install command, adjusted Lint step conditions.
.vscode/settings.json	Changed "source.fixAll.tslint" from true to "explicit".
src/GraphvizInstaller.ts, src/main.ts	Updated import quotes to double quotes for consistency.
src/__tests__/GraphvizInstaller.spec.ts	Switched to vitest, updated mocking and syntax, refactored test cases for consistency.

🐇✨
Changes here, changes there,
Quoting consistency, with care.
Yarn cached, Node upgraded,
In our code garden, improvements paraded.
🌼🚀

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between e062d7c and bd75fc3.

Files ignored due to path filters (4)

• biome.json is excluded by: !**/*.json
• package.json is excluded by: !**/*.json
• tslint.json is excluded by: !**/*.json
• yarn.lock is excluded by: !**/*.lock

Files selected for processing (5)

• .github/workflows/workflow.yaml (1 hunks)
• .vscode/settings.json (1 hunks)
• src/GraphvizInstaller.ts (2 hunks)
• src/tests/GraphvizInstaller.spec.ts (12 hunks)
• src/main.ts (1 hunks)

Files skipped from review due to trivial changes (1)

• src/main.ts

Additional comments: 22

.vscode/settings.json (1)

• 6-6: LGTM!

.github/workflows/workflow.yaml (2)

• 16-17: LGTM!
• 19-19: LGTM!

src/GraphvizInstaller.ts (5)

• 1-2: LGTM!
• 10-16: LGTM!
• 25-29: LGTM!
• 33-48: LGTM!
• 53-57: LGTM!

src/__tests__/GraphvizInstaller.spec.ts (14)

• 1-11: LGTM!
• 12-13: LGTM!
• 15-17: LGTM!
• 19-40: LGTM!
• 56-106: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [43-72]

LGTM!

• 80-89: LGTM!
• 125-146: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [115-141]

LGTM!

• 155-173: LGTM!
• 188-214: LGTM!
• 229-253: LGTM!
• 267-292: LGTM!
• 320-337: > 📝 NOTE

This review was outside the diff hunks and was mapped to the diff hunk with the greatest overlap. Original lines [310-332]

LGTM!

• 343-354: LGTM!
• 368-386: LGTM!