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

player-version-inserter

v1.0.2

Published

Project used for a Lambda function to create player version and plugin records

Downloads

6

Readme

player-version-inserter

This is a project written to be a Lambda function triggered via SNS messages. It will be used to insert new plugin and player versions into Topper Harley. The primary entry point is index.js.

Lambda Deployment

Run the following:

nvm use 6.10
rm -rf node_modules
npm install
npm install -g grunt
grunt package

This will generate pvi.zip file. This file should be uploaded to each the Lambda function (one per env) that will be using it.
This is done via the AWS Console. The Lambda function configuration should have "index.handler" set for the Handler value.

SNS

As stated above, the Lambda function will be triggered by SNS messages. Also included in this project is src/sns.js which will be used from TeamCity builds to send those messages.

The following ENV variables must be defined for SNS functionality to work:

  • export AWS_ACCESS_KEY_ID={your key}
  • export AWS_SECRET_ACCESS_KEY={your secret}
  • export AWS_REGION=us-east-1

The commands for sending the three different SNS message types are as follow:

wget http://stedolan.github.io/jq/download/linux64/jq
chmod +x ./jq
VERSION=`cat package.json | ./jq '.version'`  # This line returns something like "5.12.32"
VERSION=`echo "$VERSION" | tr -d \"`          # This removes the quotes
# or if ruby is installed
# VERSION=`ruby -rjson -e 'j = JSON.parse(File.read("package.json")); puts j["version"]'`

node src/sns.js version --version $VERSION
node src/sns.js versionReference --version $VERSION --type prerelease

node src/sns.js plugin --packageJson ~/work/git/player-version-inserter/tests/pluginPackage.json 

TeamCity and Plugins

The simplest way to add the verion inserter to your plugin pipeline in TeamCity is to add a build based on the Plugin Version Inserter template. You need to do the following:

  • add the plugin's VCS to the build with the checkout rule

    +:. => plugin
  • add a Finished Build trigger for the plugin's Publish/Deploy build with branch filter

    +:refs/tags/*

Testing

Mocha and jshint are used to validate the project. Running "grunt" alone will run both jshint and unit tests. You an also run "grunt unit" or 'grunt integration" specifically to run the specified tests (though there are no integration tests at this time).