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

@alwatroos/fgen

v1.0.5

Published

## **1. What is it for?**

Downloads

211

Readme

File Generator by ALWATROOS

1. What is it for?

This CLI is created for generating files using EJS template engine. You can define your own templates in templates directory. Each subdirectory in templates directory is treated as component template and you can list such components using fgen -ls or fgen --list commands.

2. How it works?

You define templates in templates directory using EJS markup language and FGEN do the rest for you! You can also avoid using default configs and you can create fgen.config.json file with your own custom config.

{
  "workDir": "[Optional][String] Path to work directory -> default to directory where fgen is used",
  "srcDir": "[Optional][String] Path to source directory -> default to 'src'",
  "templateSrc": "[Optional][String] Path to template directory -> default to 'templates'",
  "configPath": "[Optional][String] Path to configuration file -> default to '$WORK_DIR/fgen.config.json'",
  "debugMode": "[Optional][Boolean] Enables/Disables debug mode which writes some more data in console -> default to 'false'",
  "fileNamePattern": "[Optional][String] Naming convention for naming files with '_NAME_' variable (possible values -> 'kebab-case', 'camel-case', 'pascal-case') -> default to 'pascal-case'",
  "contentNamePattern": "[Optional][String] Naming convention for naming fields in files with 'name' variable (possible values -> 'kebab-case', 'camel-case', 'pascal-case') -> default to 'camel-case'"
}

3. Example usage

fgen -g store -v name=super -v someOtherVariable=someValue <- this command would generate component from template store with passed variables name and someOtherVariable. name variable is used for naming things inside templates (for example files -> _NAME_.ts would generate Super.ts). If you want to see all possible commands provided by fgen cli then type command fgen -h or fgen --help.

4. Credentials

Libraries used: