local-npm/local-npm

A way to cause a resync of modules that have changed while local-npm has been offline

Open

#129 建立於 2016年8月30日

在 GitHub 查看
 (6 留言) (0 反應) (0 負責人)JavaScript (1,133 star) (101 fork)batch import
bughelp wanted

描述

It would be good if there was a way to get local-npm to re-sync with the up-stream registry if local-npm wasn't running when that module changed (ie didn't get the event for the change)

貢獻者指南

技術棧
javascriptnodejs
領域
backendtooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
JavaScriptnpmNode.js
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
45
研究方向
The issue requests a resync mechanism for modules that changed while local npm was offline. To implement, examine the current sync logic in the repository, likely in the main library files. Look at how local npm receives change events from the upstream registry and how it could catch up after downtime. Check existing comments for any proposed approaches or constraints.