vitest -> bun

[binnmti]

Running Playwright does not work as expected
DOM testing

Summary by CodeRabbit

• New Features

  • Introduced a new configuration setting to preload specific files enhancing setup efficiency.
  • Added global fetch handler functionality for improved network request handling.

• Bug Fixes

  • Updated test commands and dependencies to align with new testing framework, ensuring more robust and efficient testing.

• Refactor

  • Transitioned deployment triggers from push to pull request events to enhance deployment process reliability.
  • Adjusted setup and testing paths in deployment configurations for better integration.

• Chores

  • Updated library versions in package.json to leverage improved functionality and compatibility.

• Documentation

  • Commented out a non-essential notification step in the deployment workflow for cleaner execution logs.

[coderabbitai]

Warning

Rate Limit Exceeded

@binnmti has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 16 minutes and 11 seconds before requesting another review.

How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.
Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.
Please see our FAQ for further information.

Commits

Files that changed from the base of the PR and between db688d7 and 01c8eb7.

Walkthrough

The recent updates herald a significant transformation in testing frameworks from Vitest to Bun across various configurations and test files. The deployment workflow now triggers on pull requests instead of pushes, and a new happydom.ts file emerges to manage global fetch operations. Notable changes include a configuration file for Bun and updates to dependencies.

Changes

File Path	Change Summary
.github/workflows/deploy-production.yml	Trigger updated to pull_request for main; modified Playwright setup; .env creation added; Discord webhook notification commented out.
one-pager-maker/bunfig.toml	Introduces a new setting to preload happydom.ts.
one-pager-maker/happydom.ts	Adds functionality to register a global fetch handler with bunFetch.
one-pager-maker/package.json	Test commands now use bun; @happy-dom/global-registrator added; @types/web updated.
one-pager-maker/tests/integration/redux/documentsApi.test.tsx one-pager-maker/tests/unit/sample.test.ts	Replaced vitest imports with bun:test; removed ReactNode import in integration test.
one-pager-maker/tsconfig.json	Removed "types": ["vitest/importMeta"] entry.

🐰✨
Oh hark! A change does come,
With Bun and tests, the code does hum.
From push to pull, the triggers dance,
In files and scripts, a fresh advance.
Cheers to devs, with every commit,
A hop, a skip, in the code we knit.
🌟🐇

---

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.

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.
• 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.