NativeScript / NativeScript/nativescript-cli
Updating package.json platform versions, doesn't work.
還沒有人認領這個 Issue。
- 主要語言
- JavaScript
- 星號
- 1.1k
- 分支
- 204
- 平均合併
- 1 天 9 小時
- 30 天內合併 PR
- 8
描述
Environment
- CLI: 7.x
Describe the bug
Basically because we are using NPM now to manage the dependancies; it will store a copy of the runtime in @nativescript/ios or @nativescript/android if you bump the version of the package.json file; it will bump those copies; but the copy that we create in the "platforms/ios" or "platforms/android" remains whatever was their before.
Expected behavior
That I would have the version in the package.json file.
Additional context
We might need a post install script to clean the platforms/ios or platforms/android folder on install of the runtimes, so that way the next tns command will see the platforms folder empty and re-install the platforms from the npm version that was installed.
Possible corner case is if the CLI installs the platforms version before doing a npm i; we need to verify this isn't the case.
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
先追蹤 package.json 如何更新 @nativescript/ios 和 @nativescript/android 中的執行環境複本,然後將其與現有的 platforms/ios 和 platforms/android 處理方式進行比較。確認 CLI 是否在 npm i 之前安裝平台,並評估建議的安裝後清理。完成的標準是平台資料夾使用從 package.json 安裝的版本。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- javascript
- 領域
- cli, mobile-dev
- Issue 類型
- 缺陷
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 活躍度
- 停滯
- 描述清晰度
- 基本清楚
- 新手友好度
- 30/100