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

negen

v0.3.5

Published

Component file generation based on anygen

Downloads

7

Readme

Automatically generate project scaffolding for any project using blueprints.

Install

Install globally to use the CLI.

npm install -g  negen

Install locally to use programtically.

npm install --save  negen

Configuration

Negen requires you to set the path of your blueprints and the path where you want to generate you new modules.
In your package.json add the object negen and set both paths. You can override this values using the cli options -b for blueprints_root and -m for modules_root.

//file: package.json
{
	"negen": {
		"blueprints_root": "./path/to/your/blueprints/",
		"modules_root": "./src/modules"
	}
}

Examples

ganerate a new module:

negen generate blueprint_name new_module_name

list all Blueprints:

negen list

Creating Your Blueprints

A blueprint is any direct ">" subdirectory of your blueprints_root directory.

path/to/your/blueprints_root
  +──  blueprint1
  |   └──  __name__
  |       +── __camelName__Controller.js
  |       └── __snake_name___template.json
  +──  blueprint1.ts
  └──  blueprint2
      └──  __name__
          +── Test__PascalName__.js

The __name__ string:
Any __name__ string in a directory or file name will be replaced by the new_module_name when the build process is executed.
Any __name__ string withing the content of the Blueprint files also will be replaced by the new_module_name. Likewise, any __PascalName__ string is replaced with the PascalCase, __camelName__ for camelCase, __snake_name__ for snake_case, or __kebab-name__ for kebab-case. Additionally, you can have nested items using the path portion of a generated name. for example SomePath/NameToGenerate would produce SomePath as the replacement value for __PascalPath__ (or any other supported case).

License

MIT

Authors:

Origianl anygen from [@Ma Jerez] https://github.com/M-jerez/any-generator

n3rdy.me https://github.com/n3rdyme