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

simple-project-generator

v0.14.0

Published

Simple Project Generator

Downloads

49

Readme

Simple Project Generator

Simple command line utility to create projects from project templates.

This project is inspired by the awesome Cookiecutter.

Installing Templates

$ spg add goliatone/core.io-starter-template core
$ spg add goliatone/core.io-module-template module --skip-cache

Create a new project

$ spg new core ./myProject/ --context ./path/context.json
$ spg new app
$ spg new goliatone/app
$ spg new goliatone/app ./target/

-> search template: * local cache * download from github ø option: skip-cache -> copy template to /temp: * temp-dir-cp -> collect config * look for prompt file in template ø option: skipt if -c config.json is set -> clean output dir ø option: skip-clean -> collect-files -> expand-files -> file-processor: * solve template -> copy into target

TODO:

  • [x] Conditional files:
    • [x] When an option is selected some files get added
  • [x] Create a random port number for REPL
  • [x] When we copy a template project, we might need to npm install dependencies form the prompt file.
  • [ ] Add update command
  • [ ] Add list-remote command
  • [ ] Ensure we pass context across all middleware
  • [ ] Ensure we return context across all middleware
  • [ ] Handle errors in middleware in a sane way:
    • either return context with an error or return error with ref to context.
  • [ ] Copy/write file should preserve file permissions (for executables/scripts)
  • [ ] Normalize logging, add -verbose flag
  • [ ] Take a configuration object to skip prompt
  • [ ] Add option to symlink template on add command
  • [ ] Dry run should:
    • not clean directory (delete files/folders)
    • create new directories

Middleware (tasks):

  • Should take in a context object.
  • Should return a promise
    • Should resolve the same context object, but augmented/transformed.
    • Should reject with the same context but adding an error in the form: context.errors[middleware.id] = [err1, err2... errN];

Templates

If you want to add template filters from a task you should set it in the context:

KeyPath.set(context, 'config.template.options.filters', { formatDate });

Then it would be used as:

%{date.raw | formatDate }%

Conditional files

In some instances we might include some files, directories, or npm dependencies based on some user input. For those cases we can use optional files.

Engine

It uses the jstransformer jstransformer-swig for swig