Skip to content

Conversation

@cmraible
Copy link
Collaborator

@cmraible cmraible commented May 18, 2025

no refs

Vitest is used in all these packages, but it wasn't declared as a dependency in their package.json files.

For the posts app, I recently set it up with vitest using a later version (3.4.3). This downgrades it to stay aligned with all the other packages using vitest.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 18, 2025

Walkthrough

This change updates the development dependencies in several package.json files across multiple apps. Specifically, it adds the "vitest" package at version 0.34.3 to the devDependencies of the admin-x-activitypub, admin-x-design-system, shade, and stats apps. Additionally, it downgrades the "vitest" package from version 3.1.3 to 0.34.3 in the posts app. No other dependencies, scripts, or configurations are altered, and there are no changes to exported or public entities in any of the affected packages.

Possibly related PRs

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

@codecov
Copy link

codecov bot commented May 18, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.70%. Comparing base (7979d8f) to head (52ccb49).
Report is 3 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #23382   +/-   ##
=======================================
  Coverage   72.70%   72.70%           
=======================================
  Files        1529     1529           
  Lines      110842   110842           
  Branches    13648    13648           
=======================================
  Hits        80589    80589           
+ Misses      29247    29228   -19     
- Partials     1006     1025   +19     
Flag Coverage Δ
admin-tests 48.51% <ø> (ø)
e2e-tests 72.70% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cmraible cmraible marked this pull request as ready for review May 18, 2025 08:28
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
apps/shade/package.json (1)

52-53: Review added test framework dependencies

vitest@0.34.3 is correctly added to enable unit testing, aligning with the rest of the repo.

However, mocha@10.8.2 is also newly added but is not referenced in any scripts. If Mocha is not used elsewhere, consider removing it to reduce unused dependencies.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7979d8f and 52ccb49.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (5)
  • apps/admin-x-activitypub/package.json (1 hunks)
  • apps/admin-x-design-system/package.json (1 hunks)
  • apps/posts/package.json (1 hunks)
  • apps/shade/package.json (1 hunks)
  • apps/stats/package.json (1 hunks)
🔇 Additional comments (5)
apps/posts/package.json (1)

34-34: Align testing framework version across packages

Downgrading vitest to 0.34.3 aligns this package with the versions in other apps. The test:unit script will now run with the correct version. All looks consistent.

apps/admin-x-activitypub/package.json (1)

39-40: Ensure Vite and Vitest are declared as devDependencies

Adding "vite": "4.5.14" and "vitest": "0.34.3" ensures that both the build (vite) and test (vitest) tools are available for local development and CI. The versions align with other packages in the monorepo.

apps/stats/package.json (1)

45-46: Add Vite and Vitest for dev workflows

Including "vite": "4.5.14" and "vitest": "0.34.3" in devDependencies ensures consistent tooling for local development and testing. The testing scripts (vitest commands) and dev scripts (vite) will now resolve correctly.

apps/admin-x-design-system/package.json (2)

60-60: Verify the vite-plugin-svgr addition

vite-plugin-svgr has been added, but I don’t see it referenced in the Vite configuration. Ensure that vite.config.ts (or equivalent) imports and uses this plugin; otherwise, remove it to avoid an unused dependency.


61-61: Align testing framework version

Adding vitest@0.34.3 aligns tests with other packages. The test:unit script will now run using this version.

@cmraible cmraible merged commit 0e4504b into TryGhost:main May 18, 2025
26 checks passed
@cmraible cmraible deleted the add-vitest-explicitly branch May 18, 2025 20:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant