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

liferay-module-config-generator

v1.3.3

Published

Liferay AMD modules config generator

Downloads

2,330

Readme

Liferay AMD Module config generator

Generates the config file, needed to load AMD files via combobox in Liferay

  Usage: liferay-cfgen [options] <file ...>

  Options:

    -h, --help                                   output usage information
    -b, --base [file name]                       Already existing template to be used as base for the parsed configuration
    -c, --config [config variable]               The configuration variable to which the modules should be added. Default: __CONFIG__
    -e, --extension [module extension]           Use the provided string as an extension instead to get it automatically from the file name. Default: ""
    -f, --format [module format]                 Regex and value which will be applied to the file name when generating the module name. Example: "/_/g,-". Default: ""
    -i, --ignorePath [ignore path]               Do not create module path and fullPath properties.
    -k, --keepExtension [keep file extension]    If true, will keep the file extension when it generates module name. Default: false
    -l, --lowerCase [lower case]                 Convert file name to lower case before to use it as module name. Default: false
    -m, --moduleConfig [module configuration]    JSON file which contains configuration data for the modules, for example module prefix
    -n, --namespace [namespace]                  The namespace that should be used for "define" and "require" calls. Default: ""
    -o, --output [file name]                     Output file to store the generated configuration
    -p, --filePattern [file pattern]             The pattern to be used in order to find files for processing. Default: "**/*.js"
    -r, --moduleRoot [module root]               The folder which will be used as starting point from which the module name should be generated. Default: current working directory
    -s, --skipFileOverride [skip file override]  Do not overwrite module file if name is auto generated.
    -V, --version                                output the version number