Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Chore] Package Updates #8702

Merged
merged 1 commit into from
Jan 6, 2025
Merged

[Chore] Package Updates #8702

merged 1 commit into from
Jan 6, 2025

Conversation

rahul-rocket
Copy link
Collaborator

@rahul-rocket rahul-rocket commented Jan 6, 2025

PR

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.


Summary by CodeRabbit

Release Notes

  • Dependency Updates

    • Updated zone.js to the latest patch version
    • Upgraded Angular ESLint packages to version 18.4.3
    • Updated SWC-related packages to newer versions
  • Dependency Changes

    • Removed mobx from Gauzy UI
    • Added @typescript-eslint/types
    • Added eslint package
  • Configuration

    • Removed "codelyzer" from spell-checking configuration

Copy link
Contributor

coderabbitai bot commented Jan 6, 2025

Walkthrough

This pull request involves updates to configuration and dependency management across multiple files. The changes primarily focus on updating package versions, removing certain dependencies, and adjusting spell-checking configurations. The modifications span .cspell.json, apps/gauzy/package.json, and the root package.json, with a focus on upgrading Angular ESLint packages, adjusting dependency versions, and streamlining project dependencies.

Changes

File Change Summary
.cspell.json Removed "codelyzer" from spell-check words
apps/gauzy/package.json - Removed mobx dependency
- Updated zone.js from 0.14.8 to ~0.14.10
package.json - Added @typescript-eslint/types
- Updated zone.js
- Added mobx
- Upgraded Angular ESLint packages from 18.0.1 to 18.4.3
- Updated @swc packages
- Added eslint

Poem

🐰 Dependencies dance and sway,
Versions hop from old to new today!
Mobx leaps out, ESLint takes flight,
Configurations sparkling bright!
A rabbit's code update delight! 🚀


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

@rahul-rocket rahul-rocket merged commit 5f3be79 into develop Jan 6, 2025
13 of 16 checks passed
@rahul-rocket rahul-rocket deleted the fix/packages-update branch January 6, 2025 08:26
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: 2

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3d1cdfe and 5f369ff.

⛔ Files ignored due to path filters (1)
  • yarn.lock is excluded by !**/yarn.lock, !**/*.lock
📒 Files selected for processing (3)
  • .cspell.json (0 hunks)
  • apps/gauzy/package.json (1 hunks)
  • package.json (6 hunks)
💤 Files with no reviewable changes (1)
  • .cspell.json
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: Codacy Static Code Analysis
  • GitHub Check: Socket Security: Pull Request Alerts
  • GitHub Check: test
  • GitHub Check: build
🔇 Additional comments (5)
apps/gauzy/package.json (1)

171-171: LGTM! Version sync with root package.json

The zone.js update to ~0.14.10 aligns with the version in the root package.json, maintaining consistency across the project.

package.json (4)

373-373: LGTM! TypeScript ESLint types addition

Adding @typescript-eslint/types as a resolution is appropriate for ensuring consistent TypeScript ESLint behavior across the project.


429-431: LGTM! Angular ESLint packages update

The update of @angular-eslint packages to version 18.4.3 is consistent across all related packages:

  • @angular-eslint/eslint-plugin
  • @angular-eslint/eslint-plugin-template
  • @angular-eslint/template-parser

466-468: LGTM! SWC packages update

Consistent update of SWC-related packages to their latest versions:

  • @swc-node/register: ^1.10.9
  • @swc/core: ^1.10.4
  • @swc/helpers: ^0.5.15

420-420: LGTM! Zone.js version sync

The zone.js update to ~0.14.10 is consistent with the version update in apps/gauzy/package.json.

package.json Show resolved Hide resolved
package.json Show resolved Hide resolved
Copy link

nx-cloud bot commented Jan 6, 2025

View your CI Pipeline Execution ↗ for commit 5f369ff.

Command Status Duration Result
nx serve api -c=production --prod ❌ Failed 2s View ↗

☁️ Nx Cloud last updated this comment at 2025-01-06 09:10:30 UTC

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