TypeScript: Modernize CI and dependency maintenance
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 重构
- 描述清晰度
- 需要澄清
- 活跃度
- 活跃
- 技术栈
- github-actions, nodejs, typescript, vscode
- 领域
- build-system, ci-cd, release, tooling
调研方向
首先查看 package.json、main、pre-release 和 release 工作流，以及集成测试套件，以梳理当前的 CI 和发布行为。将提议的包管理、依赖更新、lint、兼容性和 release-gating 方向与现有检查进行比较。当就一套可维护的方向达成一致，并将这项范围广泛的工作拆分为具有明确验证的、重点明确的后续变更时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Now that the immediate CI breakage is addressed in #1731, I think we should modernize the remaining development and release infrastructure so that vscode-R does not accumulate another large dependency backlog.
This does not need to be implemented in a single PR. The goal of this issue is to agree on the direction and track a series of smaller changes.
Package management and dependency updates
I would like to migrate the repository from npm to pnpm and pin the package manager version through packageManager in package.json.
After the existing dependency backlog has been reviewed and updated manually, we should enable Dependabot for both JavaScript dependencies and GitHub Actions so that future updates arrive incrementally rather than accumulating for years.
The exact pnpm version can be chosen at implementation time, taking current Dependabot support into account.
Reproducible CI and release builds
CI and release workflows should always install exactly the dependencies recorded in the lockfile.
Build and release tools such as @vscode/vsce and ovsx should also be project dependencies rather than being fetched implicitly through npx during a release.
The main, pre-release, and release workflows should use the same supported Node and Actions versions where practical.
Release gating
At present, the release workflow can package and publish the extension independently of the main test workflow.
Before future releases, we should make sure that publication can only happen from a revision that has passed the required build, lint, and test checks. This could be implemented with reusable workflows or another simple mechanism that avoids duplicating CI logic.
Test coverage and compatibility matrix
The integration test suite has improved substantially recently, so we now have a reasonable basis for routine dependency updates.
We should continue strengthening it around areas where dependency or platform changes are most likely to cause regressions, especially extension activation, R session startup/IPC, terminal integration, language-server startup, and packaging of bundled resources such as sess.
It would also be useful to explicitly test both:
- the minimum VS Code version declared in
engines.vscode - the current stable VS Code version
@types/vscode should be kept consistent with our minimum supported VS Code API rather than drifting independently.
Toolchain modernization
Some of the JavaScript/TypeScript development stack is significantly behind current releases, including TypeScript, ESLint, and typescript-eslint.
Rather than assuming that we should simply upgrade the existing ESLint stack, I think this is also a good opportunity to reevaluate the linting and formatting toolchain itself. Modern alternatives such as Oxlint/Oxfmt and Biome may provide a simpler and faster maintenance model.
We should compare them against the checks we currently rely on, especially type-aware linting, and choose based on rule coverage, TypeScript compatibility, editor/CI integration, and maintenance cost rather than preserving ESLint by default.
Possible implementation order
- Migrate npm to pnpm with frozen lockfile installs in CI.
- Align main, pre-release, and release workflows and make releases depend on successful verification.
- Review and modernize the JavaScript/TypeScript toolchain and existing dependency backlog.
- Add Dependabot for JavaScript dependencies and GitHub Actions.
- Expand the compatibility/test matrix where useful.
This work should remain separate from the proposed vscode-R 4.0 extension restructuring. A reliable and routinely maintained CI baseline should make that larger refactoring considerably safer.
- 主要语言
- TypeScript
- 星标
- 1.2k
- 派生
- 139
- 平均合并
- 22 小时
- 30 天内合并 PR
- 23
环境准备
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
REditorSupport/vscode-R 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 84/100
REditorSupport/vscode-R#1687 · 4 条评论 · 3 个 reaction ·
维护者通常 1 天内回复
-
feature-request
难度 4/5 3-5 天 新手友好度 48/100
REditorSupport/vscode-R#1780 ·
维护者通常 1 天内回复
-
REditorSupport/vscode-R#1772 · 4 条评论 · 已指派 2 人 ·
维护者通常 1 天内回复
-
feature-request
难度 4/5 3-5 天 新手友好度 45/100
REditorSupport/vscode-R#1763 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 35/100
REditorSupport/vscode-R#1755 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 REditorSupport/vscode-R 的全部 Issue
相似的 Issue
-
resources
难度 2/5 1-3 小时 新手友好度 72/100
railmapgen/rmg-palette#2445 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
danielmiessler/LifeOS#2242 ·
维护者通常 5 天内回复
-
good first issue hacktoberfest help wanted translation
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
callstackincubator/appduct#129 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 88/100