[RFC] Using a package manager for plugins
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 20/100
- Issue 類型
- 功能
- 描述清晰度
- 需要釐清
- 活躍度
- 停滯
- 技術堆疊
- javascript
- 領域
- tooling
研究方向
該 issue 沒有指出需要檢查的檔案、測試或進入點。首先釐清外掛程式探索、下載、版本管理、更新與 GitHub 備援機制的需求,然後將這些需求對應到現有的外掛程式安裝流程。完成的標準是形成共識的套件管理器設計,以及包含可測試行為的實作計畫。
由索引模型根據 Issue 內容生成。
描述
While it's still early days for plugins in Noteplan, it might make sense to keep all the "blessed" plugins in this Github repo, but longer term, that'll start to get untenable. Specially when it comes to releases.
Using a package manager like NPM might make a lot of sense. Using registry.npm.org URLs it's fairly straightforward to search, get details and download packages that can go directly to the Plugins folder.
Here are the benefits to this approach:
- Third party packages can all follow a naming convention (e.g. noteplan-plugin-commandName) and publish them on NPM and they will become easily discoverable for users.
- NPM packages have versioning built-in and it will become easy for different plug-ins to be updated independently and for Noteplan to periodically check for updates easily by package name.
- Since NPM allows for an independent
.npmignorefile it'll become easy to ignore built files for GitHub and ignore source files for the NPM package. This way Noteplan doesn't have to download any unnecessary files. - It should still be valid to use a Github URL to manually download plugins that aren't on NPM. (without all the extra feature though)
Possible downsides:
- Churn - NPM can be an additive feature so that the churn can be kept to a minimum.
- it slightly increases the barrier to entry, but it's really just an
npm publishcommand for a plug-in author. For advanced plugins this would be a total win.
- 主要語言
- JavaScript
- 星號
- 204
- 分支
- 82
- 平均合併
- 22 小時 27 分鐘
- 30 天內合併 PR
- 3
貢獻指南
這個儲存庫沒有索引到貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
NotePlan/plugins 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 74/100
-
bug
難度 4/5 3-5 天 新手友好度 48/100
-
難度 5/5 一週以上 新手友好度 35/100
-
bug
-
bug
難度 3/5 1-2 天 新手友好度 38/100
相似的 Issue
-
code-quality refactoring
難度 2/5 1-3 小時 新手友好度 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
難度 2/5 1-3 小時 新手友好度 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
難度 2/5 1-3 小時 新手友好度 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
難度 2/5 1-3 小時 新手友好度 88/100
-
難度 2/5 1-3 小時 新手友好度 88/100