remove unused apps and packages

[elg0nz]

• delete mocksi-lite
• remove old/unused packages

Summary by CodeRabbit

• New Features

  • Simplified testing process by focusing only on the reactor package.
  • Updated documentation to reflect changes in installation instructions.

• Bug Fixes

  • Removed deprecated packages from the project, which may improve stability.

• Documentation

  • Revised installation instructions to point to the new location.
  • Removed outdated documentation for certain packages.

• Chores

  • Removed multiple files related to the mocksi-lite project, indicating a significant restructuring or deprecation of features.

[coderabbitai]

Walkthrough

Walkthrough

The pull request introduces significant changes to the mocksi-lite application, including the removal of multiple components, utility files, and configuration settings. Key alterations involve simplifying the GitHub Actions workflow for testing, eliminating several packages from the README, and deleting numerous React components and utility functions related to recording and editing functionalities. This restructuring indicates a shift in focus and a potential simplification of the application's architecture.

Changes

File Path	Change Summary
.github/workflows/vitest.yml	Removed test execution steps for harlight, dodom, and mocksi-lite, retaining only reactor.
README.md	Removed references to @repo/harlight, @repo/dodom, and @repo/ui packages.
apps/mocksi-lite/MocksiRollbar.ts	Deleted Rollbar configuration file, removing integrated error tracking.
apps/mocksi-lite/README.md	Deleted README for mocksi-lite, eliminating setup and usage instructions.
apps/mocksi-lite/background.ts	Removed core functionality for Chrome extension interactions.
apps/mocksi-lite/biome.json	Deleted configuration for import organization and linting.
apps/mocksi-lite/common/*.tsx	Removed various UI components, including buttons, dividers, and icons.
apps/mocksi-lite/content/*.tsx	Deleted multiple components related to popups, settings, and user interactions.
apps/mocksi-lite/utils.ts	Removed utility functions for managing user authentication and DOM manipulation.
apps/mocksi-lite/package.json	Removed dependencies for @repo/harlight and @repo/dodom.
apps/mocksi-lite/manifest.json	Deleted entire configuration for the Chrome extension.
apps/mocksi-lite/networking.ts	Removed API call functionality and authentication handling.
apps/mocksi-lite/vitest.config.ts	Deleted Vitest configuration file, impacting the testing setup.
docs/index.md	Updated installation instructions reference to a new location.
docs/product-flow.md	Removed line about automatic timestamp updates in CLI.
packages/dodom/*.md	Deleted README and configuration files related to the DoDomCommander package.

Possibly related PRs

• [NC]: Record popup with logout functionality #19: Modifies the GitHub Actions workflow related to testing, connecting to changes in the background.ts and utils.ts files.
• [NC]: Create demo UI #23: Introduces UI components and modifies the consts.ts file, aligning with the main PR's restructuring efforts.
• [NC]: Create demo and UI fixes #29: Updates the TextField and Form components, relating to the simplification of the testing process in the main PR.
• Create demo minor fixes #30: Introduces a new Demo interface and state management in ContentApp.tsx, aligning with the main PR's focus on restructuring.
• [NC]: Get recordings integration #36: Integrates recording functionalities, relating to the main PR's changes in testing workflow.
• [NC]: Authorization api integration #44: Changes regarding authorization and API integration, connecting to the main PR's modifications in testing workflow.
• Add rollbar.js and add it to content, popup, and background #46: Adds Rollbar for error tracking, which connects to the main PR's focus on simplifying the testing process.
• More Rollbar fixes #56: Fixes related to Rollbar, which may relate to the main PR's changes in the testing workflow.
• [NC] [MOC-18] Play mode UI flow #67: UI flow changes that connect to the main PR's modifications in the testing workflow.

Poem

🐰 In the meadow where bunnies play,
Changes hop in a bright array.
Components gone, a simpler way,
Mocksi-lite shines, come what may!
With every leap, new paths we find,
A joyful dance, a leap of mind! 🌼

---

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>, please review it.
  -- 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 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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration 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.

[fitzk]

Yay!