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

log-file-remover

v0.1.20

Published

A tool to automate removal of generated logs after a set amount of time.

Downloads

27

Readme

log-file-remover

A tool to automate removal of generated logs after a set amount of time.

##Install npm install log-file-remover

##Usage

  • require the library in your code
  • entry point is index.js
var logRemover = require('log-file-remover');
logRemover.schedule(config);

##Config JSON Object The library will accept a custom config object being passed into the schedule function. If no object is passed through then the default config will be used.

##Default object passed into the scheduler unless otherwise specified.

{
    "timeZone": "Africa/Johannesburg", 
    "logging": {
        "file": {
            "folder": "/logs",
            "retention": {
                "units": "days",
                "amount": 7
            },
            "timeToTake": "mtime"
        },
        "startTheJobAutomatically": false,
        "cronTime": "* * * * *"
    }
}

If startTheJobAutomatically is set to false, remember to call job.start(), assuming job is the variable you set the cron job to. Unfortunately, for now this is hard coded to true.

For the timeZone if you need others, check the moment-timezone npm module

timeToTake is the time which will be looked at when deleting logs. timeToTake is either mtime, ctime or fileName. The modified time, the created time or a date specified in the file name. The filename looked at follows this expression: log-file-name.YYYY-MM-DDTHH

Example: crash-log.2016-01-13T14

cronTime uses standard cron input. This allows for more explicit control of the timed settings of the cron Job

##Some Examples of Cron Times:

    everySecond: '* * * * * *',
    everyMinute: '* * * * *',
    everyHour: '00 00 * * * *',
    every10Seconds: '*/6 * * * * *',
    midnight: '00 00 00 * *',
    everyDayAtTwoFifteen: '00 15 02 * * *'