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

simple-etl

v1.0.0

Published

an ETL for data transformation and loading

Readme

Simple ETL for extracting, transforming and loading data into engines

(for Now only dynamodb and appSearch engines are supported.)

How it work ?

  • use a schema Object to define the way your data should be mapped, transformed (see example below)

  • once you define your schema pass it the Etl : const ETL = new Etl(schema)

  • after that you could use one of the ETL methods : extract, transform or load

  • call the initiate method to initiate the whole ETL process

Schema Example :

// shape of data that should be submitted

const entity1 = {
  name: "entity1",
  attributes: { // define your attributes from the data source attributes
    attribute1: {
      mapTo: "AttRibute1", // here you can change the name of the attribute
      required: true, // if this attribute isn't present stop the mapping
    },
    attribute2: {
      // omit the mapTo property to use the same attribute name as described in your data source.
      map: (value) => value.split(';')[0], // if you need some logic for mapping an attribute use the map method
    },
   ....
   ....
  },
  transformations: { // if you want to add no existing attributes to your data use the transformation block
    newAttribute1: {
      transform: (item) => item.attribute1 + item.attribute2,
    },
    ....
    ....
  },
  skipIfNotExist: ["attribute3", "attribute4"], // skip this entity if those attributes aren't exist in the data source
};

// you can define as many entities as you want
const entity2 = {
  ....
  ....
  },
};


// after defining your entities
// define your engines (Now we support only dynamodb and appSearch, we welcome you to be a collaborator)

const engines = {
  dynamodb: { // define dynamodb entities and configuration
    entities: [entity1, entity2], // entities
    config: {
      tableName: "table",// name of the table , Note: your table should be already created
      config: { // actual configuration
        region: "eu-west-3", // AWS region
        accessKeyId: "accessKeyId", // accessKeyId
        secretAccessKey: "secretAccessKey", // secretAccessKey
        // endpoint: "http://localhost:8000" // use this attribute if you're working locally
      },
    },
  },

  appSearch: {
    entities: [entity1],
    config: {
      baseUrl:
        "your-base-url/api/as/v1/",
      apiKey: "private-key", // private key
      engineName: "engine1", // name of your engine
    },
  },
};

Notes:

if you want to add other custom engines feel free to collaborate to our/your library.