version-fox / version-fox/vfox
[Question] 升级到新版 current 文件夹不再使用了吗
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 4k
- Forks
- 157
- Avg merge
- 1h 3m
- Merged PRs (30d)
- 5
Description
这是我以前和现在的配置
C:\Users\29028>vfox config -l
proxy.url = http://localhost:7890
proxy.enable = true
storage.sdkPath = D:\Env\vfox\SDK
registry.address =
legacyVersionFile.enable = true
legacyVersionFile.strategy = specified
cache.availableHookDuration = 12h
以前的版本，比如nodejs ，设置vfox use -g nodejs@xxx 会索引到D:\Env\vfox\SDK\nodejs\current 文件夹中
升级后 重新选择另一个版本，就会变成到用户目录
C:\Users\29028>where npm
C:\Users\29028.version-fox\sdks\nodejs\npm
C:\Users\29028.version-fox\sdks\nodejs\npm.cmd
这是功能改进 还是存在BUG呢？
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported behavior with vfox config -l, vfox use -g nodejs@xxx, and where npm on Windows. Compare the configured storage.sdkPath and legacyVersionFile settings with the old SDK\nodejs\current path and the newer user-directory path. Done means determining whether this path change is intentional or a regression, and identifying the expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100