NativeScript / NativeScript/nativescript-cli
NativeScript SideKick doesnt work with custom npm-global directory
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 1.1k
- 派生
- 204
- 平均合并
- 1 天 9 小时
- 30 天内合并 PR
- 8
描述
Did you verify this is a real problem by searching the [NativeScript Forum]
Yes - nothing found.
Tell us about the problem
Running NativeScript sidekick errors out with Native Script CLI not found but is installed and working.
- verified by running
tns --version
My NativeScript CLI is installed into home directory /home/jay/.npm-global
Which platform(s) does your issue occur on?
iOS/Android/Both
Please provide the following version numbers that your issue occurs with:
- CLI: 3.4.3
- Cross-platform modules: NA
- Runtime(s): NA
- Plugin(s): NA
Please tell us how to recreate the issue in as much detail as possible.
-
Change default location of npm global package directory following instructions provided by npm
https://docs.npmjs.com/getting-started/fixing-npm-permissions -
Install NativeScript Sidekick for Linux
-
Run NativeScript Sidekick and get below error

Is there code involved? If so, please share the minimal amount of code needed to recreate the problem.
No
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
未指定源文件或测试。使用安装在 /home/jay/.npm-global 下的 NativeScript CLI 3.4.3 重现 Linux 情况,然后从 tns --version 检查开始跟踪 Sidekick 的 CLI 发现流程;当 Sidekick 检测到该安装,并且有一个回归测试覆盖自定义 npm-global 路径时完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, linux, nodejs
- 领域
- cli
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100