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.