added compile check

[cyri113]

Summary by CodeRabbit

• New Features

  • Introduced new scripts for linting, formatting, continuous integration, and deployment.

• Chores

  • Updated CI workflow to include a new compilation job and modified the test job to run on Ubuntu.

[coderabbitai]

Walkthrough

The recent changes introduce a new compile job in the CI workflow, setting up Node.js and running compilation steps. The existing test job is modified to run tests on Ubuntu. Additionally, the package.json file is updated with new development dependencies and scripts for linting, formatting, continuous integration, and deployment using @biomejs/biome and npx hardhat.

Changes

Files	Change Summary
.github/workflows/ci.yml	Added compile job for Node.js setup and compilation; modified test job to run on Ubuntu.
package.json	Added @biomejs/biome as a dev dependency; added scripts for linting, formatting, CI, and deployment.

Sequence Diagram(s) (Beta)

sequenceDiagram
    participant Developer
    participant GitHub Actions
    participant Node.js
    participant Yarn

    Developer->>GitHub Actions: Push Code
    GitHub Actions->>Node.js: Setup Node.js
    GitHub Actions->>Yarn: Run yarn install
    Yarn-->>GitHub Actions: Dependencies Installed
    GitHub Actions->>Yarn: Run yarn compile
    Yarn-->>GitHub Actions: Code Compiled
    GitHub Actions->>Node.js: Setup Node.js (for tests)
    GitHub Actions->>Yarn: Run yarn test
    Yarn-->>GitHub Actions: Tests Executed

Loading

Poem

In the code where changes bloom,
A rabbit hops through virtual room.
With yarn and Node, the scripts align,
To make our CI pipeline shine.
Biome's tools in package.json stay,
Ensuring code is linted all the way.
Deployments now a breeze, hooray! 🌟

---

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 testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @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.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 9205f2a and f3f6567.

Files selected for processing (1)

• .github/workflows/ci.yml (2 hunks)

Additional comments not posted (2)

.github/workflows/ci.yml (2)

9-15: The compile job configuration looks good and aligns with the PR objectives.

---

17-18: The modifications to the test job are appropriate and enhance the CI pipeline by explicitly setting the environment and improving test coverage reporting.

[coderabbitai]

Actionable comments posted: 0

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f3f6567 and e29021f.

Files ignored due to path filters (1)

• yarn.lock is excluded by !**/*.lock

Files selected for processing (2)

• .github/workflows/ci.yml (1 hunks)
• package.json (2 hunks)

Files skipped from review due to trivial changes (1)

• package.json

Files skipped from review as they are similar to previous changes (1)

• .github/workflows/ci.yml