TypeScript: Modernize CI and dependency maintenance
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 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
- 平均マージ
- 23時間 31分
- マージ済み PR（30日）
- 13
環境構築
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
REditorSupport/vscode-R のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
REditorSupport/vscode-R#1687 · コメント 4 件 · リアクション 3 件 ·
メンテナーはふだん 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 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
REditorSupport/vscode-R#1751 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 35/100
REditorSupport/vscode-R#1749 · コメント 5 件 · リアクション 3 件 ·
メンテナーはふだん 1 日以内に返信
REditorSupport/vscode-R の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 84/100
opengovsg/FormSG#10118 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
ai-driven-qa bug claude
難易度 1/5 1時間未満 初心者へのやさしさ 75/100
linagora/twake-calendar-frontend#1434 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
check:passed streams:add
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
iptv-org/iptv#52824 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 半日 初心者へのやさしさ 78/100
jaegertracing/jaeger-ui#4512 ·
メンテナーはふだん 1 日以内に返信
-
area:ide documentation enhancement platform:macos platform:vscode
難易度 1/5 1〜3時間 初心者へのやさしさ 88/100
anthropics/claude-code#97389 ·
メンテナーはふだん 1 日以内に返信