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

lambda-taggable-elasticsearch-indexer

v1.0.1

Published

Lambda that will be triggered when inserting a tag at S3 bucket and will index data into elasticsearch.

Downloads

4

Readme

Lambda Taggable Elasticsearch Indexer

Codeship codecov

Listen for updates in tags in the numo-taggy/ci S3 bucket and update ElasticSearch record.

The data inserted to ElasticSearch will be used to autocomplete at the tagging system and isearch-ui.

Tags will be created as follows:

{
  tagid: 'tagid',
  name: 'market value',
  label: 'official tag name',
  context: '`taggy` for tagging system and `market:language` for isearch-ui'
}

A tag will be created for each value in the markets property specified in the input data plus an additional tag with taggy context for taggable-ui.

For example, with the following input:

{
  "_id": "geo:geonames.1609350",
  "displayName": "Bangkok",
  "location": {
    "lat": "13.75398",
    "lon": "100.50144"
  },
  "tags": [
    {
      "node": "geo:geonames.1608132",
      "edge": "LOCATED_IN",
      "displayName": "Changwat Nonthaburi",
      "source": "geonames",
      "active": true
    }
  ],
  "markets": {
    "dk": {
      "da": {
        "label": "Bangkok",
        "values": [
          "Bangkok",
          "Vangkok"
        ]
      }
    },
    "de": {
      "de": {
        "label": "Bangkok",
        "values": [
          "Bangkok"
        ]
      }
    },
    "gb": {
      "en": {
        "label": "Angels land",
        "values": [
          "The City of Angels"
        ]
      },
      "es": {
        "label": "Bangkok",
        "values": [
          "Bangkok"
        ]
      }
    },
  }
}

The following tags would be created:

{
  tagid: 'geo:geonames.1609350',
  name: 'Bangkok',
  label: 'Bangkok',
  context: 'dk:da'
}

{
   tagid: 'geo:geonames.1609350',
   name: 'Vangkok',
   label: 'Bangkok',
   context: 'dk:da'
}

{
   tagid: 'geo:geonames.1609350',
   name: 'Bangkok',
   label: 'Bangkok',
   context: 'de:de'
}

{
   tagid: 'geo:geonames.1609350',
   name: 'The city of Angels',
   label: 'Angels land',
   context: 'gb:en'
}

{
   tagid: 'geo:geonames.1609350',
   name: 'Bangkok',
   label: 'Bangkok',
   context: 'gb:es'
}

{
   tagid: 'geo:geonames.1609350',
   name: 'Bangkok',
   label: 'Bangkok',
   context: 'taggy'
 }

Environment Variables

To run/develop/test this Lambda locally you will need to export the following Environment Variables:

export AWS_ES_ENDPOINT=yourdomain.eu-west-1.es.amazonaws.com
export AWS_S3_BUCKET=numo-taggy
export AWS_REGION=eu-west-1
export AWS_IAM_ROLE=arn:aws:iam::1234567890:role/lambdafull
export AWS_ACCESS_KEY_ID=YORKIE
export AWS_SECRET_ACCESS_KEY=SuperSecret

Copy the sample.env to .env and add the valid values for the access keys.

cp sample.env .env

if you don't have the keys get them from CodeShip

If you need to check if your environment variables are correct, try running:

node test/ping.js