Routine npm upkeep: minimatch override, vitest 5.1, stale dependabot comments

未关闭 适合新手
#116 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
82/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
devtools

调研方向

从 package.json、package-lock.json 和 .github/dependabot.yml 开始;根据 issue 检查清单审查依赖覆盖项和 Dependabot 说明。运行 npm ci && npm run lint && npm test 检查更新。完成条件:解决 minimatch 安全公告,且不降级所列工具;更新 vitest;修正过时的注释。

由索引模型根据 Issue 内容生成。

描述

dependencies good first issue severity: low

Summary

Routine npm dev-dependency upkeep, plus stale Dependabot comments. Runtime dependencies are clean.

Checklist

  • npm audit reports 10 moderate findings, all from one advisory in minimatch <11.0.1 (GHSA-g3hv-75wg-m249). It is pulled in only by dev tooling: eslint 10.14, @eslint/config-array and @typescript-eslint/typescript-estree ([email protected]). The suggested npm audit fix --force downgrades eslint and typescript-eslint, so don't use it. Instead add "overrides": { "minimatch": "^11.0.1" } and confirm npm run lint still passes, or wait for upstream.
  • vitest 5.0.5 to 5.1.0 (in range): npm update vitest, then npm test.
  • .github/dependabot.yml comments are stale:
    • line 20 says "engines is >=20 and CI runs Node 20/22", but engines is >=22.0.0 and CI runs 22/24;
    • lines 12-14 describe a zod 3 to 4 upgrade that has already landed;
    • lines 17-19 mention typescript 6.x, but the ignore also blocks the 7.x PR that #78 needs.
      Rewrite them, and point the typescript note at #78.

Not included: typescript 7.x (tracked in #78), and @types/node, which is held at ^22 to match the engines floor on purpose.

Getting started

  • Relevant files: package.json, package-lock.json, .github/dependabot.yml
  • How to run tests: npm ci && npm run lint && npm test

Filed by repo-audit/full-audit at e836036. Severity: low. Effort: S. audit-key: dependencies|package.json|minimatch

主要语言
TypeScript
星标
0
派生
6
平均合并
1 天 21 小时
30 天内合并 PR
8

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TMHSDigital/godot-correctness-mcp 的其他 Issue

查看 TMHSDigital/godot-correctness-mcp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。