fix: add @eslint/js deps declaring

[chilingling]

English | 简体中文

PR

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our Commit Message Guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• Built its own designer, fully self-validated

PR Type

What kind of change does this PR introduce?

• Bugfix
• Feature
• Code style update (formatting, local variables)
• Refactoring (no functional changes, no api changes)
• Build related changes
• CI related changes
• Documentation content changes
• Other... Please describe:

Background and solution

【问题描述】

1. 升级到 pnpm v10
2. 安装依赖 pnpm install
3. 构建插件 pnpm build:plugin
4. 发现报错
   

【解决方案】
由于缺失依赖声明，加上依赖声明就好了

What is the current behavior?

Issue Number: #1126 #1112

What is the new behavior?

Does this PR introduce a breaking change?

• Yes
• No

Other information

Summary by CodeRabbit

• Chores
  • Updated project dependencies to maintain consistency and uphold code quality standards.

[coderabbitai]

Walkthrough

The pull request adds a new dependency to the packages/common/package.json file. Specifically, it introduces "@eslint/js": "^8.57.1" in the dependencies section without altering any other parts of the file.

Changes

File(s)	Summary
packages/common/package.json	Added dependency "@eslint/js": "^8.57.1" to the dependencies.

Suggested labels

bug, ready_for_review

Suggested reviewers

• hexqi

Poem

I'm a rabbit with code in my hops,
New lines bring joy that never stops.
A dependency added to keep the linting bright,
Hop along and code through day and night.
With twitching whiskers and a carrot delight,
I celebrate these changes with every byte!

---

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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 66068fb and 43ca423.

📒 Files selected for processing (1)

• packages/common/package.json (1 hunks)

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

• GitHub Check: push-check

🔇 Additional comments (1)

packages/common/package.json (1)

36-36:

❓ Verification inconclusive

Verify the @eslint/js version.

Let's ensure we're using the latest secure version of @eslint/js.

---

🏁 Script executed:

#!/bin/bash
# Check npm registry for latest version and any security advisories
npm view @eslint/js versions --json | jq -r '.[-1]'
npm audit @eslint/[email protected]

Length of output: 439

---

Attention: Update @eslint/js Dependency & Validate Security Audit

The dependency in packages/common/package.json is currently set to "@eslint/js": "^8.57.1", but the registry shows version 10.0.0 as the latest release. This update may offer critical improvements and security fixes. Note that the npm audit command failed due to a missing lockfile. To properly audit, please:

• Update the dependency: Consider bumping the version to "^10.0.0".
• Generate a lockfile: Run npm i --package-lock-only (or your preferred lockfile generation command) to create a lockfile.
• Run a security audit: Re-run npm audit after generating the lockfile to ensure there are no vulnerabilities.