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

@antoniosbarotsis/fake-db

v0.4.1

Published

[![NPM License](https://img.shields.io/npm/l/all-contributors.svg?style=flat)](https://github.com/AntoniosBarotsis/fakeDB/blob/master/LICENSE) [![NPM Version](https://img.shields.io/npm/v/@antoniosbarotsis/fake-db?style=flat)](https://www.npmjs.com/packa

Downloads

19

Readme

NPM License NPM Version NPM Downloads

Fake-DB

What is it ?

Fake-DB reads in a json file and automatically creates various endpoints on an express server. The point of this is for it to be used as an API mock to aid front-end development.

Installation and Start-Up

Install the package with npm i @antoniosbarotsis/fake-db.

Make sure to create a data.json file at the root of your project.

To use it you just have to import it and run start()

const db = require('@antoniosbarotsis/fake-db')

db.start(8000) // Starts the server

Alternatively you can do the following:

const { start } = require('@antoniosbarotsis/fake-db')

start(8000)

The start method takes in the port and filename as an arguments. If no port is specified then process.env.PORT will be used. If that is also undefined then 8000 will be picked. The default file name is data.json.

Usage

The package picks up the objects you input at the data.json file and automatically creates endpoints for them.

If we for example have the following in the file:

{
  "users": [
    {
      "name": "Tony"
    }
  ]
}

Once we run the application endpoints will be generated under the path http://localhost:8000/users.

The file will be modified by now to this:

{
  "users": [{
      "name": "Tony",
      "id": 1
  }],
  "state": {
      "users": {
        "counter": 1
      }
  }
}

You'll see that our user has a new generated id attribute. In addition a new state object has appeared which is used to keep track of certain data that is neededbehind the scenes (as of now it only keeps track of the counters needed for id generation).

Endpoints

This might change in the future but for now for every entry in the json file the following endpoints are created (using users as an example):

  • GET /users
  • GET /users/:id
  • POST /users
  • PUT /users/:id
  • DELETE /users/:id

In other words you can: Get all users, get a specific user by his id, add a new user (needs request body) update a user by id (also requires request body) and delete a user by id.

For now the PUT request needs all of the fields a user normally has (minus the id) but in the future that might change to any number of fields.