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

kaselab

v0.0.1

Published

Command line time tracking / project management tool

Downloads

4

Readme

KaseLab

Simple command-line time tracking, designed for freelance designers/developers.

Outputs a tab-separated time report for easy import to spreadsheet software.

Installation

Requirements

  • node 4+ (0.10+)
  • npm 3+

No database requirements. KaseLab works with a single static file, ~/.kaselab.conf.json. Good practice would be to back this up regularly.

Installing

npm install -g kaselab

Usage

-> % kaselab new project BestWebApp
Any project reference? [no] myClient-002
Any client? [no] myClient
Does client have its own reference? [no]
Successfully created BestWebApp and set it as the active project

-> % kaselab use myClient-001
Successfully set active project to myClient-001

-> % kaselab timer start
Started timer on myClient-001

-> % kaselab timer stop
Description of what you did: [working] Created app framework
Stopped timer on myClient-001

-> % kaselab report myClient-001
Time report for project myClient-001
---------------------
Project initiated: Tue Jan 17 2017
Total time: 12 hrs 1 mins over 1 days.
---------------------
Date			Start	End	Description
Wed Jan 18 2017		08:46	15:46	Wireframing
Thu Jan 19 2017		14:13	19:15	Created app framework

What about broken time?

Sometimes I forget to start or stop a timer. In this case, you can just edit ~/.kaselab.conf.json and correct the mistakes.

License

This is public domain.

Contributions

Are welcome.