Update Deps

[vicb]

Summary by Sourcery

Enhance test configurations by adding CI-specific settings with coverage enabled and simplify test setup by removing explicit Jest executor configurations and outputs from project files.

Enhancements:

• Update test configurations across multiple projects to include CI-specific settings with coverage enabled.
• Remove explicit Jest executor configurations and outputs from project files, simplifying the test setup.

Summary by CodeRabbit

Release Notes

• New Features

  • Enhanced test configurations across multiple applications and libraries to support continuous integration (CI) with new options for handling tests and coverage reporting.
  • Introduced a "passWithNoTests" option to allow test execution even when no tests are present.

• Bug Fixes

  • Removed outdated executor and output configurations, streamlining the test setup.

• Dependency Updates

  • Updated various dependencies to their latest versions, improving overall project stability and performance.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the project configuration files to standardize and simplify the test setup across multiple applications and libraries. It introduces a new Jest plugin for Nx and modifies the test configurations to use a more consistent approach.

File-Level Changes

Change	Details	Files
Added new Jest plugin configuration in nx.json	Introduced @nx/jest/plugin for test and benchmark targets Specified include paths for various apps and libs	nx.json
Standardized test configuration across multiple project.json files	Removed specific Jest executor configurations Added passWithNoTests option Introduced CI configuration with coverage	apps/run/project.json libs/optimizer/project.json apps/fxc-tiles/project.json apps/fetcher/project.json apps/fxc-front/project.json apps/fxc-server/project.json apps/misc/project.json apps/proxy/project.json libs/common-node/project.json libs/common/project.json libs/vaadin-dom/project.json libs/windy-sounding/project.json
Removed specific Jest configuration files	Deleted references to individual jest.config.ts files	apps/run/project.json libs/optimizer/project.json apps/fxc-tiles/project.json apps/fetcher/project.json apps/fxc-front/project.json apps/fxc-server/project.json apps/misc/project.json apps/proxy/project.json libs/common-node/project.json libs/common/project.json libs/vaadin-dom/project.json libs/windy-sounding/project.json

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The pull request introduces modifications across various project configuration files, primarily focusing on the "test" target. Key changes include the removal of the "executor" and "outputs" properties, the addition of a new option "passWithNoTests": true, and the introduction of a "configurations" section that includes a "ci" configuration with properties set to true. These updates aim to streamline testing configurations and enhance support for continuous integration environments.

Changes

Files	Change Summary
apps/fetcher/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
apps/fxc-front/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
apps/fxc-server/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
apps/fxc-tiles/project.json	Added coverage output path; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
apps/misc/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
apps/proxy/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
apps/run/project.json	Removed "executor" and "outputs" for both test and benchmark; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
libs/common-node/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
libs/common/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
libs/optimizer/project.json	Removed lint target; added "passWithNoTests": true in test target and a new "configurations" section with "ci": { "ci": true, "coverage": true }; added empty "tags" array.
libs/secrets/package.json	Updated @nx/webpack dependency version from 19.7.2 to 19.8.0.
libs/vaadin-dom/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
libs/windy-sounding/project.json	Removed "executor" and "outputs"; added "passWithNoTests": true and a new "configurations" section with "ci": { "ci": true, "coverage": true }.
nx.json	Added new configurations for Jest plugin: "test" and "benchmark" targets with specified paths.
package.json	Updated multiple dependency versions, including various @nx packages and others.

Possibly related PRs

• Update dependencies #312: The changes in this PR involve the removal of the "executor" and "outputs" properties from the "test" configuration in libs/windy-sounding/project.json, similar to the modifications made in the main PR for apps/fetcher/project.json. Both PRs also introduce the "passWithNoTests": true option and a new "configurations" section for CI, indicating a related focus on updating test configurations.

Poem

🐇 In the land of code, changes abound,
With tests that now pass, no matter what's found.
Executors gone, outputs in flight,
Continuous integration shines ever so bright!
With options anew, our projects will thrive,
Hooray for the changes, our code comes alive! 🌟

---

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

[sourcery-ai]

Hey @vicb - I've reviewed your changes - here's some feedback:

Overall Comments:

• Could you clarify why the lint configurations were removed from some projects (e.g., optimizer)? Is linting being handled differently now?

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[cloudflare-workers-and-pages]

Deploying flyxc with    Cloudflare Pages

Latest commit:	7ffca57
Status:	✅  Deploy successful!
Preview URL:	https://7a2fb392.flyxc.pages.dev
Branch Preview URL:	https://virtual-branch.flyxc.pages.dev

View logs