sindresorhus/conf

Support using a Conf store from multiple processes

Open

#146 opened on Mar 11, 2021

View on GitHub
 (4 comments) (0 reactions) (0 assignees)TypeScript (138 forks)user submission
enhancementhelp wanted

Repository metrics

Stars
 (1,340 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate file locking mechanisms (e.g., lockfile library) or atomic writes to prevent concurrent process clobbering in the conf package.
Tech stack
typescriptnodejs
Domain
backenddeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Node.jsfile system basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50