Security News
Weekly Downloads Now Available in npm Package Search Results
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
key-file-storage
Advanced tools
Simple key-value storage directly on file system, maps each key to a separate file.
const store = require("key-file-storage")('my/storage/path')
// Write something to file 'my/storage/path/myfile'
store.myfile = { x: 123 }
// Read contents of file 'my/storage/path/myfile'
const x = store.myfile.x
// Delete file 'my/storage/path/myfile'
delete store.myfile
A nice alternative for any of these libraries: node-persist, configstore, flat-cache, conf, simple-store, and more...
Installing package on Node.js:
$ npm install key-file-storage
Initializing a key-file storage:
// ES Modules import style:
import kfs from 'key-file-storage'
// CommonJS import style:
const kfs = require("key-file-storage")
const store = kfs('/storage/directory/path', caching)
The value of caching
can be
true
(By default, if not specified) : Unlimited cache, anything will be cached on memory, good for small data volumes.
false
: No cache, read the files from disk every time, good when other applications can modify the files' contents arbitrarily.
n
(An integer number) : Limited cache, only the n
latest referred key-values will be cached, good for large data volumes where only a fraction of data is being used frequently .
As simple as native javascript objects:
store['key'] = value // Write file
store['key'] // Read file
delete store['key'] // Delete file
delete store['*'] // Delete all storage files
'key' in store // Check for file existence
//=> true or false
You can use store.keyName
instead of store['keyName']
anywhere if the key name allows.
undefined
is not supported as a savable value, but null
is. Saving a key with value undefined
is equivalent to remove it. So, you can use store['key'] = undefined
or even store['*'] = undefined
to delete files.
Synchronous API will throw an exception if any errors happen, so you shall handle it your way.
Every one of the following calls returns a promise:
store('key', value) // Write file
store('key') // Read file
new store('key') // Delete file
new store('*') /* or */
new store() /* or */
new store // Delete all storage files
('key' in store(), store()) // Check for file existence
// Resolves to true or false
undefined
is not supported as a savable value, but null
is. Saving a key with value undefined
is equivalent to remove it. So, you can use store('key', undefined)
or even store('*', undefined)
to delete files.The same as asynchronous with promises, but with callback function as the last input parameter of store()
:
store('key', value, cb) // Write file
store('key', cb) // Read file
new store('key', cb) // Delete file
new store('*', cb) /* or */
new store(cb) // Delete all storage files
'key' in store(cb) // Check for file existence
// without promise output
/* or */
('key' in store(), store(cb))
// Check for file existence
// with promise output
These calls still return a promise on their output (except for 'key' in store(callback)
form of existence check).
The first input parameter of all callback functions is err
, so you shall handle it within the callback. Reading and Existence checking callbacks provide the return values as their second input parameter.
Every folder in the storage can be treated as a collection of key-values.
You can query the list of all containing keys (filenames) within a collection (folder) like this (Note that a collection path must end with a forward slash '/'
):
try {
const keys = store['col/path/']
// keys = ['col/path/key1', 'col/path/sub/key2', ... ]
} catch (error) {
// handle error...
}
store('col/path/')
.then(keys => {
// keys = ['col/path/key1', 'col/path/sub/key2', ... ]
})
.catch(error => {
// handle error...
})
store('col/path/', (error, keys) => {
if (error) {
// handle error...
}
// keys = ['col/path/key1', 'col/path/sub/key2', ... ]
})
NOTE 1 : Each key will map to a separate file (using the key itself as its relative path). Therefore, keys may be relative paths, e.g: 'data.json'
, '/my/key/01'
or 'any/other/relative/path/to/a/file'
. The only exception is strings including '..'
(double dot) which will not be accepted for security reasons.
NOTE 2 : You may have hidden key files by simply add a '.'
before the filename in the key path.
NOTE 3 : If a key's relative path ends with a forward slash '/'
, it will be considered to be a collection (folder) name. So, 'data/set/'
is a collection and 'data/set/key'
is a key in that collection.
NOTE 4 : This module has a built-in implemented cache, so, when activated, accessing a certain key more than once won't require file-system level operations again for that file.
NOTE 5 : When activated, caching will include queries on collections too.
NOTE 6 : For TypeScript developers, you may indicate the store's value type when creating it: const store = kfs<DataType>(...)
.
import kfs from "key-file-storage"
interface User {
readonly name: string
readonly skills: Readonly<Partial<Record<string, number>>>
}
// Locate 'db' folder in the current directory as the storage path,
// Require 100 latest accessed key-values to be cached:
const store = kfs<User>('./db', 100)
// Create file './db/users/hessam' containing this user data, synchronously:
store['users/hessam'] = ({
name: "Hessam",
skills: {
java: 10,
csharp: 15
}
})
// Read file './db/users/hessam' as a JSON object, asynchronously:
store('users/hessam').then(hessam => {
console.log(`Hessam's java skill is ${hessam.skills.java}.`)
})
// Check whether file './db/users/mahdiar' exists or not, asynchronously:
'users/mahdiar' in store((error, exists) => {
if (exists) {
console.log("User Mahdiar exists!")
}
})
// List all the keys in './db/users/', synchronously:
const allUsers = store['users/']
//=> ['users/hessam', 'users/mahdiar', ... ]
It would be very appreciated if you had any suggestions or contribution on this repository or submitted any issue.
FAQs
Simple key-value storage directly on file system, maps each key to a separate file.
The npm package key-file-storage receives a total of 160 weekly downloads. As such, key-file-storage popularity was classified as not popular.
We found that key-file-storage demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Socket's package search now displays weekly downloads for npm packages, helping developers quickly assess popularity and make more informed decisions.
Security News
A Stanford study reveals 9.5% of engineers contribute almost nothing, costing tech $90B annually, with remote work fueling the rise of "ghost engineers."
Research
Security News
Socket’s threat research team has detected six malicious npm packages typosquatting popular libraries to insert SSH backdoors.