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

@ando_ghevian/create-project

v1.2.0

Published

organization scoped create-project cli tool

Downloads

50

Readme

CreateProject

This is simple CLI Tool to create projects from Templates scoped to specific user or organsization.

Usage

There is two ways to use create-project:

  1. By Installing it globaly
  2. Via npx

Global Install

Steps for first case(global install)

  1. First lets install it globaly, npm i -g @ando_ghevian/create-project
  2. Set scope from which you want to download templates (Templates start with cpj-template[-templatename]), create-project scope set @ando_ghevian
  3. Check that everything went smoothly, and scope is accepted create-project scope get
  4. Create Project From: create-project --template npm-package my-package

You can also use another scope when creating project:

  • create-project scope use @elseScope --template temp prj
  • create-project use @elseScope --template temp prj (use is alias for scope use)

You can create project when setting scope:

  • create-project scope set @ando_ghevan -t npm-package my-package

You can also use templates from url, and in this case you dont need any scope to be set.

  • create-project -t git+https://[email protected]:AndoGhevian/cpj-template-npm-package.git proj

WORNING: Be shore that you specify protocol!!!

You can just test your local Templates:

  • create-project -t file:../../MyTemplate prj
  • create-project -t file:/path/from/root/to/template prj

NOTE: See below "How to create Templates"

NPX

Steps For npx:

  • npx @ando_ghevian/create-project use @Scope --template tmp prj
  • npx @ando_ghevian/create-project -t git+https://[email protected]:AndoGhevian/cpj-template-npm-package.git proj

How to create Templates

It's similar to create-react-app Custom Templates. Just few differences:

  1. Templates from npm registry must be scoped to organization or user and fit the format cpj-template[-templatename], where cpj-template will be used as default if --template(-t) is specified without value (Or not specified).
  2. You can Use Templates also from Code Hosting Platforms like github and gitlab. In this case scope is not needed. And Template Name can be anything, i.e. no need to start with cpj-template. Template just HAS TO stick to the rules, that we have defined.
  3. Default Key/Value Pairs of created projects package.json file, come from npm init -y command, and anything you specify in template.json in /package property, will replace default ones.
  4. You MUST NOT specify package.json, package-lock.json and node_modules/ in template folder (/template). They will be simply ignored.
  5. And Currently We will replace all {{ProjectName}} occurrences in README.md with your project name.