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: Update npm dependencies to latest versions #197

Merged
merged 1 commit into from
Jul 31, 2024

Conversation

amengus87
Copy link
Collaborator

@amengus87 amengus87 commented Jul 31, 2024

Summary by CodeRabbit

  • Chores
    • Updated various libraries and dependencies to their latest versions to enhance security and functionality.
    • Changed the script command for updating packages to improve performance and reliability.
    • Minor version updates for axios dependencies, indicating maintenance improvements.

These updates ensure a more stable and secure application without introducing significant changes to existing features.

Copy link

coderabbitai bot commented Jul 31, 2024

Walkthrough

The recent changes involve updating several dependencies across the frontend packages, enhancing overall stability and performance. Key libraries like dayjs, naive-ui, and pinia have received minor version bumps, reflecting routine maintenance and bug fixes. Additionally, the build script command for update-pkg has been updated, suggesting a shift in the package management approach. These updates are crucial for maintaining security and compatibility with newer features.

Changes

File Path Change Summary
frontend/package.json Updated multiple dependencies including dayjs, naive-ui, pinia, vue, typescript, and others to their latest versions. Modified update-pkg script command.
frontend/packages/axios/package.json Updated axios-retry from 4.4.1 to 4.4.2 and qs from 6.12.2 to 6.12.3.
frontend/packages/scripts/package.json Updated rimraf from 5.0.7 to 6.0.1.

Possibly related issues

  • Dependency Dashboard #189: The changes in this PR directly address updates listed in the Dependency Dashboard, specifically for dependencies like rimraf, dayjs, and naive-ui.

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>.
    • 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 show all the console.log statements in this repository.
    • @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 as 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.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.

Copy link

sonarcloud bot commented Jul 31, 2024

Copy link

@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

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 4deb10e and 84cee67.

Files selected for processing (3)
  • frontend/package.json (2 hunks)
  • frontend/packages/axios/package.json (1 hunks)
  • frontend/packages/scripts/package.json (1 hunks)
Files skipped from review due to trivial changes (2)
  • frontend/packages/axios/package.json
  • frontend/packages/scripts/package.json
Additional comments not posted (13)
frontend/package.json (13)

40-40: Verify the new update-pkg script command.

The command has been updated from dRAGon update-pkg to pnpm dragon-frontend update-pkg. Ensure that pnpm is properly configured and that this new command works as expected.


52-52: Verify dayjs update.

The dayjs dependency has been updated from 1.11.11 to 1.11.12. Ensure that this minor update does not introduce any breaking changes or issues.


55-55: Verify naive-ui update.

The naive-ui dependency has been updated from 2.38.2 to 2.39.0. Ensure that this update does not introduce any breaking changes or issues.


57-57: Verify pinia update.

The pinia dependency has been updated from 2.1.7 to 2.2.0. Ensure that this update does not introduce any breaking changes or issues.


59-59: Verify vue update.

The vue dependency has been updated from 3.4.31 to 3.4.35. Ensure that this update does not introduce any breaking changes or issues.


67-67: Verify @iconify/json update.

The @iconify/json dependency has been updated from 2.2.223 to 2.2.232. Ensure that this update does not introduce any breaking changes or issues.


71-71: Verify @types/node update.

The @types/node dependency has been updated from 20.14.10 to 22.0.0. Ensure that this update does not introduce any breaking changes or issues.


81-81: Verify eslint update.

The eslint dependency has been updated from 9.6.0 to 9.8.0. Ensure that this update does not introduce any breaking changes or issues.


84-84: Verify sass update.

The sass dependency has been updated from 1.77.6 to 1.77.8. Ensure that this update does not introduce any breaking changes or issues.


86-86: Verify typescript update.

The typescript dependency has been updated from 5.5.3 to 5.5.4. Ensure that this update does not introduce any breaking changes or issues.


89-89: Verify vite update.

The vite dependency has been updated from 5.3.3 to 5.3.5. Ensure that this update does not introduce any breaking changes or issues.


92-92: Verify vite-plugin-vue-devtools update.

The vite-plugin-vue-devtools dependency has been updated from 7.3.5 to 7.3.7. Ensure that this update does not introduce any breaking changes or issues.


94-94: Verify vue-tsc update.

The vue-tsc dependency has been updated from 2.0.26 to 2.0.29. Ensure that this update does not introduce any breaking changes or issues.

Copy link

codecov bot commented Jul 31, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

@amengus87 amengus87 merged commit 8dea533 into staging Jul 31, 2024
6 checks passed
@amengus87 amengus87 deleted the upgrade-frontend-dependencies-20240731 branch July 31, 2024 09:26
amengus87 added a commit that referenced this pull request Jul 31, 2024
chore: Update npm dependencies to latest versions (#197)
amengus87 added a commit that referenced this pull request Aug 2, 2024
* chore: Update RaagService to include SiloRepository (#197)

* Renaming route home to operations-center

* Operations Center updates

* Adding fake endpoints on backends to allow auth

* On 404 error, deliver index.html (SPA)

* Begin using pre-commit to lint over files

* chore: Refactor OpenAiCompatibleV1ApiControllerTest to improve code readability and remove unused imports

* chore: Add ErrorHandlerController to handle errors and deliver index.html on 404 error (SPA)

* Updating frontend dependencies

* chore: Update operations center to fetch numbers on page activation

* refactor: Rename header-banner.vue to infrastructure-overall.vue and card-data.vue to jvm-cards.vue

* Improving how to retrieve env vars for Testing

* Frontend : adding infrastructure overall

* chore: Update npm dependencies to latest versions

* chore: Add error handling for delivering index.html on 404 error (SPA)

* refactor: Update icons in jvm-cards.vue for better visual representation

* chore: Add SystemMonitoringServiceTest for system monitoring functionality
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