Skip to content

Reconsider custom HTTP transport for package discovery #1851

Open

Description

@eitsupi

PR #1849 preserves legacy package-discovery behavior for authenticated/private repositories, redirects, compressed responses, and repositories using ports blocked by the Fetch API.

It is unclear whether these cases are actively used or should remain part of vscode-R's long-term compatibility contract. Much of this behavior existed because it happened to work with the previous node-fetch implementation.

For vscode-R 4.0, reconsider whether we should keep the custom HTTP transport, or simplify package discovery to standard Fetch behavior and leave specialized repository access to R itself.

Activity

  1. added this to the 4.0.0 milestone on Oct 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions