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