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

woog

v1.0.4

Published

simple wrapper of @openapitools/openapi-generator-cli, with some default configurations

Downloads

4

Readme

woog

  • simple wrapper of @openapitools/openapi-generator-cli, with some default configurations.
  • woog means Wrapper Of Openapi Generator
  • if use generator openapi or openapi-yaml, paths and schemas in input file will be sorted

Install

npm i -g @openapitools/openapi-generator-cli woog

Usage

woog <generatorDirName> [inputFileName=openapi] [outputDirName=out]

example:

woog openapi
woog html2 openapi.json out.html2

Config

if config file exists(<generatorDir>/config.yaml or <generatorDir>/config.yml or <generatorDir>/config.json) generator will use it

you can put optional extra parameters in the config file:

  • x-generator

    if the generatorDir is not the same as generator name, you can set generator name with this parameter. eg: the generatorDir is java-spring-code and the generator name is spring

  • x-template

    if you want to use custom templates, set your template root dir to env OPENAPI_TEMPLATE_ROOT(eg. D:\workspace\github\openapi-generator\modules\openapi-generator\src\main\resources), and add parameter x-template to config file.

    • true means use OPENAPI_TEMPLATE_ROOT/generatorName as template dir
    • string value means use OPENAPI_TEMPLATE_ROOT/<x-template value> as template dir
    • some generators have special template dir name(different from generator name). these generators' template dir will be auto mapped if x-template have been set to true. for example:
      1. html2 -> htmlDocs2
      2. spring -> JavaSpring
      3. jaxrs-cxf -> JavaJaxRS
      4. jaxrs-cxf-cdi -> JavaJaxRS

Note

  • use openapi-generator-cli version-manager list to switch openapi-generator-cli version(if download too slow, you can manually copy org.openapitools:openapi-generator-cli:.jar to <npm prefix dir>/node_modules/@openapitools/openapi-generator-cli/versions/, remember to rename it as format <version>.jar, like 6.0.0.jar)
  • use openapi-generator-cli list to get available generator names
  • use openapi-generator-cli config-help -g <generatorName> to get generator config schema

License

MIT © rainmanhhh