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

@ochuzor/todo.txt-parser

v3.2.2

Published

a parser for todo.txt

Downloads

112

Readme

A javascript parser for todo.txt

Is it over-engineered? Yes! It is! But in my defence, the real reason for creating this package is to learn. I mean, there are a lot of good todo.txt parsers out there. This one is just for my learning purpose.

npm i @ochuzor/todo.txt-parser

The library provides a few functions for working with todo.txt formatted strings. To convert a todo.txt text into a javascript object, use:

import {textToDto} from '@ochuzor/todo.txt-parser';
const todo = textToDto('x work on the new +projectMakeOver @home');

The returned object has the following properties:

interface IDoc {
    id?: string | number;
}

interface TagDto {
    name: string;
    value: string;
}

interface TodoDto extends IDoc {
    description: string;
    isCompleted: boolean;
    priority: string;
    dateOfCreation: string;
    dateOfCompletion: string;
    projects: string[];
    contexts: string[];
    tags: TagDto[];
}

Another function provided is todoDtoToText. It converts an object from the above function into a todo.txt string. Here's how to use it:

import {todoDtoToText} from '@ochuzor/todo.txt-parser';

const todo = {
    description: 'write a new documentation',
    isCompleted: true,
    priority: '(A)',
    ...
};

const todoTxt = todoDtoToText(todo);
// returns "x (A) write a new documentation"

The priority ranges from (A) to (E). The implementation follows the format on todo.txt. The third function is textToIndexDto. It is similar to textToDto above except that every field is a string, including the "isCompleted", which is then either "true" or "false". The projects list is now a space separated list of projects. Same applies to the contexts field as well. The tags field is a space separated list of tagName:tagValue strings. I made this function, for cases where you want to index documents but make all the fields searchable strings.

Finally, I made this library for learning purposes. Check out the code and tests.