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

todo-to-be-core

v0.11.2

Published

todo manager core library

Downloads

6

Readme

To-Be

To list management customised to how I want to work to help be do what I need to, to be where I want to be.

Idea

Principles

  • Cross platform. I need to be able to work on my todos on laptop, or mobile
  • Offline & online. I need to be able to work offline but have things synced and accessible online
  • Extensible. I want todos to be accessible to additional services I might chose to create such that I can access and process them in novel ways.

Things to Capture

  • title
  • notes
  • contexts
  • Projects
    • Suggest implement as a task with child tasks.
  • Dependencies. Capture dependencies on other tasks, people, and dates. Tasks with no dependencies are automatically next actions. Tasks who's dependencies are fulfilled can be flagged for review, or automatically become next actions
  • Time estimates.
  • reminders
  • due dates
  • Date created
  • History? Need to think about how to capture this. Do we want to capture an event log as a primary data structure? Implementatin note: yaml is possibly well suited for an append only log since it does not require any closing (or opening) tags for an array
  • Composable contexts and filters.
  • value tags for categorising the value realised

Views

Want views to support the primary gtd activities

Next Actions

Show things which can be done now, prioritised as best as possible with sufficient context to understand them.

Style

Probably needs to be a tree view for best context.

Filtering

Display a todo if it, or any of it's children, match the current filter. Would filter with active contexts and possibly prompt for available time if not passed.

Sorting

Sort by:

  1. Due date
  2. Possibly Explicit priority?
  3. Possibly preferred tags?
  4. Possibly Number of matched contexts?

Useage

Installing

Create an alias in your bash_profile or equivalent along the lines of: alias todo='node ~/code/to-be/build/src/cli/index.js' Optionally set currently active contexts using ACTIVE_CONTEXTS environment variable, possibly using script such as: alias todo='ACTIVE_CONTEXTS=$(context.sh) node ~/code/to-be/build/src/cli/index.js'

View todos

todo list

Optionally filter out todos with an estimate greater than your available time with --available-time flag. For example to exclude todos estimated to take longer than 30 minutes use the command todo list --available-time 30

Create Todos

todo create 'this is a todo; @home #example-tag t=10 due=2020-10-20'

The command to create a todo is todo create this requires a single argument which is the todo's title. Tags, contexts, due date and time estimates can optionally be specified following a semicolon folowing the syntax shown in the example above.