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

@pcg/pcg

v0.3.3

Published

Project Core Generator

Downloads

8

Readme

Project Core Generator

Install

PCG should be installed globally on your local machine.

npm install -g @pcg/pcg

Usage

Firstly you should create config file called pcg.config.js in the root directory of new project.

And simply run the generator. It will do all the work

pcg 

If you've changed schema or config you could update project with the same command

pcg

Most of existing files will not be modified. If you want PCG to overwrite the old files, run

pcg --overwrite

Project types

PCG allows to create and support any type of project. Here is list of planned and available projects to create:

  • Loopback API (ready)
  • Javascript Library (in development)
  • Vue Admin (in development)

Loopback API

Node.js API server based on Loopback v3 framework. API endpoints created from OpenAPI v2 schema. So you should create OAS2 schema before generating the code.

Example of pcg.config.js

module.exports = {
    type: 'loopback',
    name: '@dv/ping',
    shortname: 'ping',
    description: 'Ping API',
    author: {
        name: 'Main Author',
        email: '[email protected]',
    },
    contributors: [
        {
            name: 'Other Author',
            email: '[email protected]',
        },
    ],
    repository: {
        name: 'Ping API',
        host: 'git.deepvision.team',
        path: 'dv/ping/api',
    },
    license: 'file LICENSE.md',
    headers: [
        {
            name: 'author',
            value: '💧DeepVision <[email protected]>',
        },
    ],
    js: {
        nodeVersion: 10,
        babel: {
            plugins: [
                '@babel/plugin-proposal-optional-chaining',
                '@babel/plugin-proposal-class-properties',
                '@babel/plugin-proposal-object-rest-spread',
                '@babel/plugin-proposal-export-default-from',
            ],
        },
    },
    loopback: {
        datasource: {
            type: 'mongo',
            user: 'ping',
            pass: 'ping',
            database: 'ping',
        },
        oas2: '/common/oas2.json',
        middlewares: [
            {
                stage: 'auth',
                path: './middlewares/auth',
                params: {},
            },
            {
                stage: 'parse',
                path: 'body-parser#json',
                params: {},
            },
        ],
    },
};

type – project type, should be "loopback"
name – project name, used in package.json
shortname – short project name, used in source code when needed, should be alphanumeric only
description – project description, used in package.json
author and contributors – used in package.json
repository – used for Gitlab repository synchronization