[164] installed npm check updates

[UgzSourceCode]

• Do ADR how to check updates
• Install npm check updates - https://www.npmjs.com/package/npm-check-updates
• Check which packages need updates

• Update packages

• updated diary

Summary by CodeRabbit

• New Features

  • Added a new script to easily check for npm package updates in the web app.

• Dependency Updates

  • Updated multiple dependencies in the web app to their latest versions, including react, typescript, vite, and various Storybook addons.

• Documentation

  • Added ADR 014 discussing tools for checking library updates.
  • Updated the diary with entries detailing recent package updates.

[coderabbitai]

Warning

Review failed

The pull request is closed.

Walkthrough

The recent updates involved adding a new script to the root package.json for checking package updates in the web-app directory using npm-check-updates. Additionally, various dependencies in the web-app's package.json were updated to their latest versions. Documentation was also updated to reflect these changes, including a new ADR describing the decision to use npm-check-updates.

Changes

Files/Paths	Change Summary
package.json	Added a new script web-app:ncu to run ncu for web-app/package.json and added npm-check-updates as a dev dependency.
web-app/package.json	Updated multiple dependencies including @emotion/styled, framer-motion, i18next, react, typescript, vite, and several Storybook packages.
docs/ADR/README.md	Added a reference to ADR 014 about the tool for checking library updates.
docs/diary.md	Added a new entry for 12-06-2024 detailing tasks related to updating packages and README descriptions.
docs/ADR/014-which-tool-for-checking-library-updates.md	New ADR discussing the decision to use npm-check-updates for managing library updates.

Poem

In the world of code, updates are bright,
New scripts and tools bring joy to the night.
Packages refreshed, dependencies aligned,
With ncu in place, all versions are fine.
A rabbit's delight, in this digital dance,
Our project now prances, given the chance.

---

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>.
  • 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 Configration 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.

[coderabbitai]

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 0fca449 and a8c0116.

Files ignored due to path filters (2)

• package-lock.json is excluded by !**/package-lock.json
• web-app/package-lock.json is excluded by !**/package-lock.json

Files selected for processing (2)

• package.json (1 hunks)
• web-app/package.json (1 hunks)

Additional comments not posted (4)

package.json (2)

10-10: The addition of the web-app:ncu script is correctly implemented and aligns with the PR objectives to manage package updates efficiently.

---

16-16: The addition of npm-check-updates to devDependencies is appropriate and necessary for the new web-app:ncu script to function.

web-app/package.json (2)

20-27: Dependencies have been updated to newer versions. Ensure that these updates do not introduce breaking changes or compatibility issues.

---

30-47: DevDependencies have been updated to newer versions. Verify that these updates do not affect the development environment or the build process adversely.