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

pastaga

v1.0.0-beta01

Published

Simple scaffolding tool using git repository for providing templates.

Downloads

2

Readme

Pastaga

Simple scaffolding tool using git repository for providing templates.

npm i -g pastaga

Requires node > 6.0

Concepts

Pastaga does not provide any generator but it synchronizes with git repository to execute code.

Repository must respect the following specific structure :

\
+- command1
 +- index.js (code to execute)
 +- manifest.json (optional description file)
+- command2
 +- index.js
 ...

You can create many context each with a different repository. Repositories are synchronized on every execution.

How to use it

Pastaga has been initially created to use with vulcainjs project.

A default context is defined referencing the vulcainjs code template repository.

This repository provides commands for initialize a new project or generate artefacts. This is a good example to see how to create your own commands.

For example, try pastaga init --template vulcain-service to create a new vulcainjs micro service.

How to create its own commands

  1. Create a new github repository
  2. Add a folder named 'MyCommand'
  3. Add it a file named index.js with the following code.
class Context {
    *prompts() {
      yield { name: 'name', type: 'input', message: "What's your name"};
    }

    exec() {
        console.log("Hello " + this.state.name);
    }
}

exports default = Context;
  1. Commit and publish your changes
  2. Set Pastaga to use your context with: pastaga context mycontext --address <git repository address>
  3. Run Pastaga with

pastaga : Display a list of commands to select. In this case, only one : MyCommand

pastaga MyCommand : Run directly your command by requesting your name.

pastaga MyCommand --name Boy : Execute your command and display Hello Boy

Manifest.json

You can add an optional manifest.json file close to the index.js to customize your command. The following properties are allowed:

| Name | Description | Default value | |-----|-----|------| | name | Command name | Folder name | | entryPoint | Context file name | index.js | | state | Initial state | {} | | description | Command description | | | order | Display order | 100 |

Command context class

Context class inherit two properties:

  • state which contains every command options (from initial state and prompts)
  • context object exposing execution context properties. See source code for details.

exec can return a command name which will be executed in the current context.

Prompts

Prompts uses inquirer.

Prompts are made in order thanks to the generator function.

Using a generator function allows you to change question based on the previous answer.

Prompt are displayed only if there is no value defined.

Execution context

You can switch between context with pastaga context <name>

You can update a context with pastaga context <name> [--address <address>] [--branch <branch>] [--set key=value]*

set is used to set global initial state. Use unset key to remove a value.

You can force a context in a command scope by adding --context <name> to the command line.