chore: Update dependencies in package.json.

[junhaoliao]

Description

1. In package.json, update dependencies & devDependencies to their latest versions.
2. Generate new package-lock.json on Windows with nvm-windows installed:

   rm -r -Force .\node_modules\
   rm package-lock.json
   
   nvm install 22
   nvm use 22.12.0
   npm i
   

3. "monaco-editor": "0.52.0" was skipped due to errors thrown at

   yscope-log-viewer/src/components/Editor/MonacoInstance/index.tsx

   Line 94 in af322a6

   editorRef.current?.dispose();

   1. The issue was observed with any version above v0.51.0-dev-20240801 (v0.51.0-dev-20240731 was the last working version).
      
   2. Issues have been reported at [Bug] Editor throws error on dispose after upgrade from 0.51 to 0.52 microsoft/monaco-editor#4702 two months ago and [Bug] Unmounting component in react throws error microsoft/monaco-editor#4779 two weeks ago but there has not been responses from maintainers.
4. Remove unused variable in src/utils/url.ts so that it does not fail linter check.

Validation performed

1. IRv2 (structured IR) log level filtering now works:
   
   Steps to generate test files can be found at feat: Add support for log-level filtering of structured IR streams. clp-ffi-js#35
2. Performed all auto / manual tests in https://docs.yscope.com/yscope-log-viewer/main/dev-guide/contributing-validation.html

Summary by CodeRabbit

• Dependency Updates

  • Updated multiple dependencies to their latest versions, including React, MUI, Axios, and Day.js.
  • Refreshed development dependencies such as Babel, TypeScript, ESLint, and Webpack.

• URL Utility Improvement

  • Simplified error handling in URL generation utility.

[coderabbitai]

Walkthrough

The pull request involves updates to the project's package.json and a modification in the src/utils/url.ts file. The package.json changes primarily focus on updating various dependencies to their latest versions, including React, MUI, Axios, and other development tools. In the url.ts file, the getAbsoluteUrl function's error handling has been simplified, removing explicit error referencing while maintaining the core URL construction logic.

Changes

File	Change Summary
package.json	- Updated multiple dependencies to newer versions - React bumped to ^19.0.0 - MUI, Emotion, Axios, and other packages updated - DevDependencies refreshed to latest versions
src/utils/url.ts	- Modified getAbsoluteUrl function error handling - Removed explicit error parameter in catch block - Simplified URL construction approach

Possibly related PRs

• new-log-viewer: Add bundle size optimization tooling; Replace JoyUI path imports with default imports. #73: Updates package.json with new dependencies, directly related to the dependency version changes
• new-log-viewer: Ensure all static assets are copied from /public to /dist during the build process (fixes #95). #96: Modifies package.json by adding a new dependency, aligning with the dependency update trend

Tip

CodeRabbit's docstrings feature is now available as part of our Early Access Program! Simply use the command @coderabbitai generate docstrings to have CodeRabbit automatically generate docstrings for your pull request. We would love to hear your feedback on Discord.

---

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.

[junhaoliao]

Maybe in the final commit message we should mention log-level filtering support as well.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (2)

src/utils/url.ts (1)

14-14: Removing the caught error may hinder debugging

Since the error object is no longer captured, it eliminates the possibility of logging or inspecting the underlying cause in complex scenarios (e.g. malformed URL inputs). Consider preserving or logging the error for troubleshooting.

package.json (1)

58-58: Assess new mini-css-extract-plugin functionalities

Make sure the build pipeline’s CSS extraction remains unaffected. Upstream changes could alter the default extraction or bundling.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between af322a6 and 016affb.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• package.json (1 hunks)
• src/utils/url.ts (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

src/utils/url.ts (1)

Pattern **/*.{cpp,hpp,java,js,jsx,ts,tsx}: - Prefer false == <expression> rather than !<expression>.

🔇 Additional comments (9)

package.json (9)

28-37: Updating dependencies to newer versions

These updated dependencies appear compatible based on the semver ranges. Continue monitoring release notes for breaking changes from major library updates (e.g. React).

---

40-43: Maintaining synergy between Babel presets

Keep an eye on Babel’s version updates and watch for potential plugin deprecations or changes to the compilation pipeline. Be prepared to run regression tests.

---

46-48: Upgraded Node and React type definitions

Ensuring that these updated definitions align with the supported Node/React versions is essential for accurate IntelliSense and type checking.

---

49-51: ESLint plugin upgrades

Confirm that lint rules remain consistent with project code style after these changes. Some ESLint plugins may introduce stricter or shifted defaults.

---

55-56: Refined import resolver settings

This upgrade should help with TypeScript path resolutions. Continue verifying that module resolution works seamlessly for all TS aliases.

---

61-62: Prettier upgrade

The new version may introduce changes to code formatting rules. Consider verifying that your existing config still formats the code as expected.

---

64-64: Stylelint version bump

Confirm that no new mandatory rules were introduced that might conflict with your coding guidelines.

---

70-71: TypeScript major revision

Be mindful of stricter type checks or newly enforced compiler flags. Consider testing thoroughly across your codebase to avoid surprises.

---

73-75: Webpack ecosystem updates

These changes could impact your dev server and production builds. Pay special attention to performance-related changes and plugin ecosystem compatibility.