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

tblue

v0.2.1

Published

Trello blueprints, scaffolding for trello boards (a.k.a. yeoman for trello)

Downloads

10

Readme

Tweet License: MIT version contributions welcome

Demo

Result: Sample generated board

💡 Motivation

If you use trello a lot, it's likely that you have common tasks based on past experience and also custom cards for a given project. Wouldn't it be nice to have some sort of blueprint or template we could use to bootstrap our boards? This project aims to solve this need.

🔧 Prerequisites

This project requires 2 environment variables set. Please add them to your .bash_profile or wherever they are needed for your environment. Next you'll find which variables you need to set and what value you should use for each one.

(You can optionally just run tblue and the cli will guide you 😉)

TRELLO_API_KEY

Log into trello and copy the developer key from https://trello.com/app-key. Use that value for this environment variable. Api Key

APP_TOKEN

Use your api key from last step and replace API_KEY inside the next url https://trello.com/1/authorize?key=API_KEY&name=tblueScaffoldingForTrello&expiration=never&response_type=token&scope=read,write

Now copy/paste the full url into your browser

Api Key

Grant access to the script so you get a token, only you know what this token is so only your local instance of tblue will use it.

Api Key

Now place the token as the value for this environment variable.

🏃 How to run

npm install -g tblue
tblue

📜 Workflow

  1. Choose a name for your board
  2. Choose which blueprint you want to use
  3. Start answering Y/n for each question in the blueprint
  4. Start adding specific "features" for your project
  5. Open your new board from the terminal 👶

CLI options

|Command option| Description| |---------------|-----------| |-h or --help|Shows all available command line options| |-c or --custom-blueprints-folder| Allows passing a folder containing one or multiple blueprints (see Custom blueprints). Only the files immediately inside the folder that have a .blueprint.json extension and have a valid template will be evaluated|

Custom blueprints

The custom blueprints you create must have the following format. If they don't, they will not show up in the blueprints selection screen.

{
    //Name that will be prompted in the CLI
    "name": "Simple API",

    //The name you give to features for your particular blueprint. e.g. feature, endpoint, article, etc
    "unitOfWork": "feature",

    //Questions that could generate a card according to your project's need
    "questions": [
        {
            "content": "Will you be using Docker?",
            "cardToGenerate": {
                "name": "Create Docker configuration"
            }
        },
    ],

    //These are cards that will always be generated when you use this blueprint
    "cards": [{"name": "Repository configuration"}]
}

Note: If you want store your custom blueprints without having to pass alwas the -c flag. You can store them in the ~/.blueprints folder

Running locally

npm install
npm start

Run tests

npm test

Contributing

Compatibilty

Emojis don't show correctly in windows' cmd 💔