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

curriculum-plan-tool

v1.3.11

Published

This tool allows to generate a plan based on a **csv file** or a project. To run the app perform `npm start` with parameters, examples see below.

Downloads

21

Readme

Study plan generator

Introduction

This tool allows to generate a plan based on a csv file or a project. To run the app perform npm start with parameters, examples see below.

Plan

The csv file has to consist of two columns:

  • title - title of a plan item (if a title is a subtask title then the title should look like group task title|task title). If you need to add all plan items you can use special title ALL_ITEMS. In this case all a container items will be included in a plan. If a plan has a tasks group the first task will be added.
  • container - container title of the plan item. You have to use folder name.

There is an example in root directory plan.csv.

To generate a plan you need to run the tool with the next arguments:

  • type=plan by default it is plan so you can skip it
  • filePath=filePath path to a csv file. By default it is plan.csv so if your path is the same you can skip it
  • renderType=html by default it is html so you can skip it. For now the tool support only html type.

A task can have "Depends on" part with list of task which results can be used in the current task. The list must be a list of relative links to tasks of the current container. So a list item will be like * [A task title](../task-folder/readme.md). Group tasks haven't been supported yet. Depended tasks will be rendered at the end of output index file.

Project

To generate a project you need to run the tool with the next arguments:

  • type=project
  • projectTitle=projectTitle you have to use folder name as a name. For example beer-catalog
  • renderType=html by default it is html so you can skip it. For now the tool support only html type.

filePath isn't used for the project command.

Validation

To validate containers you need to run the tool with the next arguments:

  • type=validation
  • containers=container-name you have to use folder name as a name. For example nodejs-testing

Technical

Install nodejs. Current node and npm versions can be found in package.json in engines section.

Run npm install --production in the app directory.

You have to use two different commands to generate a plan or a project.

Run:

  • plan - npm start [type=plan] [filePath=plan.csv] [renderType=html] in the app directory.
  • project - npm start type=project projectTitle=projectTitle [renderType=html] in the app directory.

If everything is ok outcome folder will be created. The same outcome folder will be used for a plan and a project.