sindresorhus/conf

Support using a Conf store from multiple processes

Open

#146 建立於 2021年3月11日

在 GitHub 查看
 (4 留言) (0 反應) (0 負責人)TypeScript (1,340 star) (138 fork)user submission
enhancementhelp wanted

描述

Currently if you have multiple processes using conf with the same storage location they can, and do, clobber each other's data.

e.g.

  1. p1 reads store
  2. p2 reads store
  3. p1 writes store
  4. p2 writes store (this clobbers p1's changes in step 3, even if the change was a totally different key)

Any suggestions on how to work around this?

I feel like this could warrant a big disclaimer in the readme.

貢獻者指南

技術棧
typescriptnodejs
領域
tooling
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Node.jsasync programmingfile system operations
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The issue describes a race condition when multiple processes read/write the same config store. A solution likely requires file locking or atomic writes. Investigate Node.js `fs` module for file locking mechanisms (e.g., `fs.open` with exclusive flag) or use a library like `proper lockfile`. The existing code uses `fs.writeFileSync` and `fs.readFileSync`; consider switching to `writeFile` with atomic rename. Look at issue comments for any suggested approaches.