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

cleanuptool

v1.2.2

Published

Program to clean up you Alexa dev skill list, lambda function and logs after a skill is no longer neeeded.

Downloads

9

Readme

CleanUp - A tool to help cleaning up after an Alexa Skill has served its purpose

As an Alexa Skills enthusiast, I am constantly creating skills to try out new features. Because of this, there is always a large number of skills, lambda functions and log groups that are left behind in my developer account.

I created this small script in order to help mitigate this issue. After creating, deploying, modifying, logging, breaking, fixing and breaking again (basic developer life, amirite??) all you have to do is execute this script in the skill's root folder. It will delete the skill, the lambda function associated with it and the logs associated with the lambda function. However, the files will still be in your local server, in case you wish to deploy the skill again.

The behavior explained above is the default one. This script has a set of options that will allow you to choose what to delete.

Installing

Via npm:

$ npm install cleanuptool

Usage

While in the skill's root folder (the folder that contains at least the folders lambda, models and the file skill.json, but mainly the hidden .ask folder), execute:

$ cleanUp

and your account will get cleared of the skill and it's appendages.

BUT WAIT!! That is not all! Let's say you only want to remove the skill, but leave the lambda function and the logs alone. All you have to do is use the -s flag followed by your skillID :

$ cleanUp -s [skillID]

There are 3 other flags:

  • -g [functionName]: this flag, followed by the functionName will delete the log groups associated with the function name;
  • -l [functionName]: this flag, followed by the functionName will delete the lambda function;
  • -h: this will print out a help message;