fix: 🐛 remove swc configs

[zhumeisongsong]

Summary by CodeRabbit

• Chores
  • Streamlined internal configurations by removing outdated transformation and build settings.
  • Cleaned up internal metadata and build target definitions to simplify ongoing maintenance.

[coderabbitai]

Walkthrough

This pull request removes several configuration files and build target definitions across multiple libraries. The .swcrc files used for JavaScript/TypeScript compilation have been deleted, and the build targets in various project.json files have been eliminated, resulting in empty configurations. Additionally, the package.json file for the self-care-tasks application module has been removed.

Changes

File(s)	Change Summary
libs/ai/domain/.swcrc, libs/self-care-tasks/application/.swcrc, libs/self-care-tasks/domain/.swcrc, libs/shared/infrastructure/deepseek/.swcrc	Deleted SWC/JSC configuration files containing compiler settings and transformation options.
libs/ai/domain/project.json, libs/self-care-tasks/application/project.json, libs/self-care-tasks/domain/project.json, libs/shared/.../deepseek/project.json	Removed build target configurations, leaving an empty or reduced targets object.
libs/self-care-tasks/application/package.json	Deleted package metadata and configuration file.

Possibly related PRs

• feat: ✨ delete build command in open-ai lib #137: Involved deletion of .swcrc files and removal of build targets in project configuration files.
• feat: ✨ add self-care-tasks-domain #158: Addressed modifications in build configurations and project structure for the self-care-tasks libraries.
• feat: ✨ add @ai/domain #160: Directly related changes that involve altering configuration files and build targets in a manner similar to this PR.

Suggested labels

released

Poem

I'm a little rabbit, hopping with glee,
Leaving behind files that used to be.
No more targets to build the maze,
Configurations gone in a clear new phase.
I nibble on code with a joyful cheer,
Hoping simplicity will always be near! 🐇

---

📜 Recent review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 15b66d5 and 647a4ef.

📒 Files selected for processing (9)

• libs/ai/domain/.swcrc (0 hunks)
• libs/ai/domain/project.json (1 hunks)
• libs/self-care-tasks/application/.swcrc (0 hunks)
• libs/self-care-tasks/application/package.json (0 hunks)
• libs/self-care-tasks/application/project.json (1 hunks)
• libs/self-care-tasks/domain/.swcrc (0 hunks)
• libs/self-care-tasks/domain/project.json (1 hunks)
• libs/shared/infrastructure/deepseek/.swcrc (0 hunks)
• libs/shared/infrastructure/deepseek/project.json (0 hunks)

💤 Files with no reviewable changes (6)

• libs/shared/infrastructure/deepseek/project.json
• libs/self-care-tasks/application/.swcrc
• libs/self-care-tasks/application/package.json
• libs/ai/domain/.swcrc
• libs/self-care-tasks/domain/.swcrc
• libs/shared/infrastructure/deepseek/.swcrc

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: test / Nx Test

🔇 Additional comments (3)

libs/ai/domain/project.json (1)

7-7: Empty "targets" Object in ai-domain Configuration

The removal of the build target configuration is intentional per the PR’s objective. Please ensure that any downstream build or deployment processes that depended on these settings have been updated accordingly.

libs/self-care-tasks/domain/project.json (1)

7-7: Removal of Build Targets in Self-Care Tasks Domain

The "targets" field is now an empty object, which aligns with the decision to remove SWC and related build configurations. Confirm that this change does not disrupt any tooling or scripts that previously relied on a defined build process.

libs/self-care-tasks/application/project.json (1)

7-7: Empty "targets" in Self-Care Tasks Application

Eliminating the build target configuration meets the PR objective of removing SWC configs and build definitions. Verify that the removal is reflected in the overall build and deployment strategy to prevent any unintended breakages.

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[github-actions]

🎉 This PR is included in version 1.36.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀