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 🙏

© 2025 – Pkg Stats / Ryan Hefner

swagger-codegen-next

v0.1.9

Published

根据swagger.json生成api文件

Readme

generate .ts api files by swagger.json

📦 Install

npm install swagger-codegen-next -g
yarn global add swagger-codegen-next

🔨 Usage

Configuration File

swagger-codegen.config.js

// swagger-codegen.config.js
const path = require("path");
const cwd = process.cwd();

module.exports = {
  // swagger文件地址
  url: "http://***/swagger.json",
  // 输出目录
  output: {
    path: path.join(cwd, "services"), // default
  },
  // 获取接口模块名称
  getModuleName(url) {
    return /api\/([^\/]*)/.exec(url)[1];
  },
  // 获取接口名
  getMethodName(operationId) {
    return operationId;
  },
  // 需要跳过生成的接口
  exclude: [],
  template: {
    http: 'import http from "../http";'
  }
};

Now you can run the swagger-codegen-next:

swagger-codegen-next

Config

*url

  • support HTTP/HTTPS

    {
      "url": "http://***.swaggger.json" // https://***.swagger.json
    }
  • support absolute path

    {
      "url": path.resolve(__dirname, "./swagger.json")
    }

*output

The output property tells swagger-codegen-next where to emit the api files .

{
    output: {
        path: path.join(cwd, 'services') // default
    },
}

*getModuleName

The getModuleName method can help swagger-codegen-next to group the APIs.

{
  getModuleName(url){
    return /api\/([^\/]*)/.exec(url)[1]
  }
}

getMethodName

add getMethodName to support to customize the name of a method.

exclude

skip target swagger paths

eg:

exclude: ["/api/user/add"]

LICENSE

MIT