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 🙏

© 2026 – Pkg Stats / Ryan Hefner

mukeba-repository

v1.1.2

Published

Provide an abstract repository layer for Mukeba

Readme

Mukeba Repository Package

Is a package/library that is an abstraction layer for Mukeba services. To avoid having to write the same code over and over again we can use this package.

It is a collection of functions that are used to interact with AWS services such as S3 and DynamoDB.

Package Structure

The package is structured as follows in src directory:

  • index.tx file :
    • Pulls all the environment variables from .env file and exports them as constants.
    • Checks if the required environment variables are present and throws an error if they are not.
  • definitions.ts file :
    • Contains all the types/models, enums and constants used in the package.
  • service :
    • Exposes functions that are required by the dependent services. We will try by all means possible to only access functions that are exposed in this folder in the services.
  • storage :
    • Exposes functions that required by the services in service folder.
    • dynamo-store :
      • This folder contains functions that configure and interact with DynamoDB. this is where we running CRUD operations.
    • s3-store :
      • This folder contains functions that configure and interact with S3. this is where we uploading, downloading and deleting files.
  • ses :
    • Configure and Exposes functions that deal with sending emails. These functions are used/called by mail.service.ts in service folder.
  • test :
    • Contains all the tests for the package. We are using jest to run the tests.

Terraform

Terraform is a tool that is used to provision and manage infrastruc◊ture as code. The terraform terraform folder contains all the terraform files that are used to provision the infrastructure. for now we are using terraform to provision the following resources:

  • AWS S3 bucket
  • AWS DynamoDB table

To run terraform

From now on we are running the terraform process through github actions. Any changes to the terraform files will trigger the terraform process on you pull request. the Apply of the plan will br triggered on merge.

The destroy process will be triggered manually when needed.

To publish the package

Now we are running the npm publish process through github actions. ⚠️ Please make sure that the package is built and tested before pushing your pr. ⚠️ Also make sure to update the version in package.json file before pushing your pr. ⚠️ Finally provide a comprehensive description of the changes made in the pr.

npm run build
npm run test

However if you wish to perform a publication on your local you can follow the following process:

  • npm run build
  • npm pack
  • npm login
  • npm publish --access public

ERD

classDiagram
    imageData <|-- ArticleImage
    imageData <|-- MarcheImage
    imageData <|-- PropertieImage
    Marche <-- MarcheImage
    Article --> User
    Marche --> User
    Propertie --> User
    Propertie --> PropertieImage
    Article <-- ArticleImage

    class Article {
        id: string HK
        categoryId: string GI
        ownerId: string GI
        marcheId: string GI
        villeName?: string GI
        ....
    }

    class ArticleImage {
        id: string HK
        data: imageData
    }

    class Marche {
        id: string HK
        ownerId: string GI
        villeName?: string GI
    }
    class MarcheImage {
        id: string HK
        data: imageData
    }

    class User {
        user-pk: string PK
        user-sk: string SK
        email: string GI
    }

    class Propertie {
        id: string PK
        marcheId: string GI
        ownerId: string GI
        villeName?: string GI
    }

    class PropertieImage {
        id: string PK
        data: imageData
    }