Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Bug：Windows 下 Bun 换源功能异常

Open
  • Is something wrong?
#399 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
bun, c, powershell
Domain
cli, devtools

Research direction

Start by tracing the Bun handling and command execution paths used by chsrc get bun and chsrc set bun, then inspect the source detection shared with the js/javascript/node/nodejs aliases. Reproduce the reported commands on Windows 11 PowerShell with Bun 1.4.3 installed through Scoop. Done when get reports the current source and set detects available mirrors or clearly reports that none are configured.

Written by the indexing model from the issue text.

Description

你操作了什么？

在 Windows PowerShell 环境下，尝试使用 chsrc 查看 Bun 当前源并自动换源。

  1. 执行 chsrc get bun
  2. 执行 chsrc set bun
  3. 执行 chsrc ls bun 查看 Bun 的支持情况
发生了什么？

执行 chsrc get bun 时出现以下错误：

The system cannot find the file specified.
[chsrc 运行] x 命令执行失败，退出状态: 1
chsrc: 关键错误，强制结束

执行 chsrc set bun 时出现以下提示：

[chsrc 测速] 进行中
chsrc: 当前 js/javascript/node/nodejs 无任何可用源，请联系维护者: chsrc issue

但执行 chsrc ls bun 时，可以看到 Bun 支持 Get、Reset、UserDefine，以及项目级和用户级换源功能。

目前无法确定是命令调用异常、配置问题还是 Bun 换源食谱实现问题。

本应该怎么样？

希望 chsrc get bun 能正常显示 Bun 当前的源状态，chsrc set bun 能正常检测可用镜像并完成换源。

如果目前没有预设镜像，希望能给出明确的提示，而不是出现上述错误。

chsrc 版本

v0.2.7

你使用的是哪个操作系统？

Windows

OS 版本 / OS 发行版

Windows11，PowerShell

Log 输出
命令：chsrc get bun

The system cannot find the file specified.
[chsrc 运行] x 命令执行失败，退出状态: 1
chsrc: 关键错误，强制结束

命令：chsrc set bun

[chsrc 测速] 进行中
chsrc: 当前 js/javascript/node/nodejs 无任何可用源，请联系维护者: chsrc issue

Bun 版本：1.4.3
Bun 安装方式：Scoop
防止重复问题
  • 我已在项目中搜索过类似的 issue
Dominant language
C
Stars
6.9k
Forks
285
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from RubyMetric/chsrc

All issues in RubyMetric/chsrc

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.