Dependencies Update

[marwan37]

This PR includes the following dependency updates (initiated by dependabot):

• Bump @types/node from 22.13.9 to 22.13.10
• Bump eslint-config-prettier from 9.1.0 to 10.1.1
• Bump webpack from 5.94.0 to 5.98.0
• Bump @types/vscode from 1.92.0 to 1.98.0
• Bump fs-extra from 11.2.0 to 11.3.0

Changes:
Fixed type compatibility issue with @types/vscode 1.98.0 by updating iconPath properties to use Uri objects instead of string paths.

Summary by CodeRabbit

• Chores
  • Upgraded several dependencies to the latest versions, enhancing stability and ensuring smoother development workflows. These updates support performance improvements and better integration with current ecosystem standards.

[coderabbitai]

Walkthrough

The pull request updates several dependency version numbers in the project's package.json file. In the devDependencies section, versions for @types/node, @types/vscode, eslint-config-prettier, and webpack have been incremented. In the dependencies section, the version for fs-extra has been updated. Additionally, changes in the EnvironmentItem.ts file include modifications to import statements, the addition of two class properties, and updates to the determineIcon method's signature and implementation.

Changes

File	Change Summary
package.json	- Updated @types/node from ^22.13.8 to ^22.13.10 - Updated @types/vscode from ^1.92.0 to ^1.98.0 - Updated eslint-config-prettier from ^9.1.0 to ^10.1.1 - Updated webpack from ^5.94.0 to ^5.98.0 - Updated fs-extra from ^11.2.0 to ^11.3.0
src/views/activityBar/environmentView/EnvironmentItem.ts	- Added property pythonLogo in class EnvironmentItem - Added property zenmlLogo in class EnvironmentItem - Updated method signature for determineIcon in class EnvironmentItem from `{ light: string; dark: string }

Possibly related PRs

• Bump dependencies to resolve Dependabot alerts #109: Relates to similar updates in the @types/node dependency.

Suggested labels

dependencies

Suggested reviewers

• strickvl

Poem

Hi, I'm a rabbit with a coding knack,
Hopping through updates on a well-worn track.
Dependencies fresh as a springtime carrot 🥕,
Each version bump a delightful merit.
I nibble on code and cheer with a clap,
Celebrating changes with a happy rap!
Keep on coding, let no bug trap!

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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

🧹 Nitpick comments (1)

src/views/activityBar/environmentView/EnvironmentItem.ts (1)

17-18: Consider using VSCode's extension context for resource paths

While storing paths as class properties is good for reusability, using relative paths with __dirname might be problematic in certain VSCode environments (especially web extensions). Consider using vscode.Uri.joinPath with the extension's context for more robust resource handling.

- pythonLogo = path.join(__dirname, '..', 'resources', 'python.png');
- zenmlLogo = path.join(__dirname, '..', 'resources', 'logo.png');
+ // Initialized in constructor using context
+ pythonLogo: Uri;
+ zenmlLogo: Uri;

And in the constructor:

constructor(
  public readonly label: string,
  // ... other params
  private readonly extensionContext: vscode.ExtensionContext
) {
  super(label, collapsibleState);
  this.pythonLogo = vscode.Uri.joinPath(extensionContext.extensionUri, 'resources', 'python.png');
  this.zenmlLogo = vscode.Uri.joinPath(extensionContext.extensionUri, 'resources', 'logo.png');
  // ...
}

📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9c35999 and e576791.

📒 Files selected for processing (1)

• src/views/activityBar/environmentView/EnvironmentItem.ts (3 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

`**/*.ts`: Review the Typescript code for conformity with in...

**/*.ts: Review the Typescript code for conformity with industry standards and best practices, highlighting any deviations.

• src/views/activityBar/environmentView/EnvironmentItem.ts

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

• GitHub Check: build-and-test

🔇 Additional comments (4)

src/views/activityBar/environmentView/EnvironmentItem.ts (4)

13-14: LGTM: Import changes for using Uri

The import changes look good. Switching to a namespace import for 'path' and adding 'Uri' to the VSCode imports aligns with the updated implementation.

---

38-40: LGTM: Updated method signature

The return type of determineIcon has been correctly expanded to include Uri types, which aligns with VSCode's API and the implementation changes below.

---

66-68: LGTM: Enhanced icon implementation

The implementation now uses Uri.file() with the class properties, which is cleaner and more consistent than previous approach.

---

72-74: LGTM: Enhanced icon implementation

Similar to the Python logo change, using Uri.file() with class properties provides a cleaner implementation for the ZenML logo.