npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@bpleco/fsdb

v0.0.1

Published

File System Database

Downloads

5

Readme

FSDB

File System DB is designed as a lightweight FS Database.

import { Document } from '@pitwall/fsdb';

interface SettingsSchema {
  x: boolean;
  testing: Partial<{ x: number; y: number }>;
}

const settings = new Document<SettingsSchema>({
  electronChildProcess: false,
  defaultValue: {
    testing: {
      x: 123,
    },
  },
});

const result = await settings.create({ x: false, testing: { x: 21 } });

await settings.update({ x: true, testing: { y: 42 } }, result.fileId);

const data = await settings.read(result.fileId);

console.log(data);

await settings.delete(result.fileId);

})();

Electron Child Processes are a first class citizen

import { Document } from '@pitwall/fsdb';
import { AppSettingsModel } from '@pitwall/types';
import { SetGameSettingsPayload } from 'src/shared/types';

try {
  // this is because the electron APIs are not avaible in the child process
  // its a tiny bit clunky but i think the best solution when you have state
  // that needs to be managed in both processes
  const { app } = require('electron');

  const dataPath = app.getPath('userData');

  process.env['FSDB_STORE_PATH'] = dataPath;
} catch (error) {}

export const settingsStore = new Document<AppSettingsModel>({
  electronChildProcess: true,
  fileId: 'settings',
  defaultValue: {
    currentGameSlug: 'acc',
    isInitialized: false,
    currentGame: 'acc',
    acc: {
      address: 'localhost',
      cmdPassword: '',
      gameTitle: 'Assetto Corsa Competizione',
      password: 'asd',
      port: 9000,
      slug: 'acc',
    },
  },
});

export async function setGameSettings(_event: any, settings: SetGameSettingsPayload) {
  const savedSettings = await settingsStore.read();
  await settingsStore.update({ [savedSettings.currentGameSlug]: { ...settings.settings } });
}

export async function getGameSettings() {
  return await settingsStore.read();
}