Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Make sess dependencies optional with an arf-backed transport

オープン
  • 何か問題がありますか？
#1,859 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
12/100
issue の種類
リファクタリング
明瞭さ
説明が足りない
活発さ
活発
技術スタック
r, rust, typescript
領域
developer-experience, devtools

調査の方向性

This is an architecture proposal with no comments and no agreed scope, so it is not a starting point for a first contribution. Before any code, read the linked eitsupi/arf#112, #1739, #1829 and #1856 to see which transport boundaries are already decided. Done would be a maintainer-agreed design that separates the sess transport layer from its runtime functionality, with the dependency list for the arf-backed path settled.

索引モデルが issue の本文から書いたものです。

説明

Motivation

vscode-R relies on the bundled sess package for session integration, including workspace inspection, viewers, and editor communication.

Although sess is now a pure R package, it still requires third-party dependencies such as processx, later, jsonlite, and rstudioapi.
These complicate installation, particularly in isolated environments managed by renv, pixi, etc.

PR #1856 improves installation isolation but does not eliminate these dependencies.

Meanwhile, arf already provides an IPC server implemented in Rust, potentially making much of sess's R-based communication infrastructure unnecessary.

Goal

Enable vscode-R session integration through arf without requiring third-party R packages.

This does not necessarily mean eliminating sess itself. Its pure-R runtime functionality could remain available while delegating communication to arf.

Ordinary R consoles and other frontends should continue using the existing sess transport.

Proposed direction

  • Separate transport from runtime functionality. Reuse sess's existing workspace, viewer, and runtime integration logic across different transports.
  • Use arf's IPC server. Extend its generic capabilities where necessary, particularly for structured R queries and event notifications, without introducing vscode-R-specific APIs.
  • Make dependencies optional. Remove processx, later, and jsonlite requirements from the arf-backed path, and make rstudioapi integration optional. Existing uses outside the transport layer will also need attention.
  • Integrate incrementally. Start with ordinary arf terminals and subsequently consider R Interactive, reusing existing abstractions where appropriate.

Scope

This is a long-term architectural direction, not a proposal to replace sess entirely or remove support for other R frontends.

The goal is to reduce installation requirements without duplicating session functionality or compromising compatibility.

Related

  • eitsupi/arf#112: Generic IPC server and earlier integration discussions
  • #1739: Runtime and transport lifecycle separation
  • #1829: Keeping sess a pure R package
  • #1856: Managed sess installation
主要言語
TypeScript
スター
1.2k
フォーク
147
平均マージ
1日 7時間
マージ済み PR（30日）
75

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

REditorSupport/vscode-R のほかの issue

REditorSupport/vscode-R の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。