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

ts-document

v0.8.0

Published

Auto generate ts document schema by ts interface conform to the [TSDoc](https://tsdoc.org/).

Downloads

240

Readme

ts-document

Auto generate ts document schema by ts interface conform to the TSDoc.

Highlight

  • Controllable parameter extraction, only the specified interface is extracted.
  • Automatically analyze extends relationships.
  • Support extract English and Chinese in one ts file.
  • Support generate markdown string directly.

Usage

npm i ts-document -D
const { generate, generateMarkdown } = require('ts-document');

generate('interface.ts', config);

generateMarkdown('interface.ts', config);

interface.ts

ts-document will only extract interface and type with jsDoc tag title

import { ReactNode } from 'react';

/**
 * @title Alert
 *
 * @zh
 *
 * 向用户显示警告的信息时,通过警告提示,展现需要关注的信息。
 *
 * @en
 *
 * Display warning information to the user. the Alert is used to display the information that needs attention.
 */
export interface AlertProps {
  /**
   * @zh 自定义操作项
   * @en this is action
   * @version 2.15.0
   */
  action?: ReactNode;
  /**
   * @zh 是否可以关闭
   * @en Whether Alert can be closed
   * @defaultValue false
   */
  closable?: InnerProps;
}

interface InnerProps {
  /**
   * @zh 位置
   * @en position
   */
  position?: string;
  /**
   * @zh 尺寸
   * @en Size
   */
  size?: string;
}

Generate jsDoc schema

const { generate } = require('ts-document');

generate('interface.ts');

output

{
  "Alert": {
    "data": [
      {
        "name": "action",
        "type": "ReactNode",
        "isOptional": true,
        "tags": [
          {
            "name": "zh",
            "value": "自定义操作项"
          },
          {
            "name": "en",
            "value": "this is action"
          },
          {
            "name": "version",
            "value": "2.15.0"
          }
        ]
      },
      {
        "name": "closable",
        "type": "InnerProps",
        "isOptional": true,
        "tags": [
          {
            "name": "zh",
            "value": "是否可以关闭"
          },
          {
            "name": "en",
            "value": "Whether Alert can be closed"
          },
          {
            "name": "defaultValue",
            "value": "false"
          }
        ]
      }
    ],
    "tags": [
      {
        "name": "title",
        "value": "Alert"
      },
      {
        "name": "zh",
        "value": "向用户显示警告的信息时,通过警告提示,展现需要关注的信息。"
      },
      {
        "name": "en",
        "value": "Display warning information to the user. the Alert is used to display the information that needs attention."
      }
    ]
  }
}

Generate markdown document

const { generateMarkdown } = require('ts-document');

generateMarkdown('interface.ts');

output

{
  "Alert": "### Alert\n\nDisplay warning information to the user. the Alert is used to display the information that needs attention.\n\n|Property|Description|Type|DefaultValue|Version|\n|---|---|---|---|---|\n|action|this is action|`ReactNode`|`-`|2.15.0|\n|closable|Whether Alert can be closed|`InnerProps`|`false`|-|"
}

Config

defaultTypeMap

Record<string, { type: string, tags?: TagType[] }>

If no comments are extracted, will extracted from the defaultTypeMap automatically.

sourceFilesPaths

string | string[]

See ts-morph

strictComment

boolean

Whether to skip parsing documentation comment like /** Some comment **/ as property description if there is no tag like @en or @zh.

strictDeclarationOrder

boolean

Generate schema in the order their declarations appear in the document. When it's true, generate/generateMarkdown will return an array list(Array<{ title: string; schema: Schema }>).

propertySorter

(a: { name: string; type: string; isOptional: boolean; tags: Array<{ name: string; value: string }>; }, b: typeof a) => number

The compare function to sort properties/arguments of schema generated.

lang

string

Only work in generateMarkdown, specify output language.

project

Project

Custom project to use in generate/generateMarkdown function. See ts-morph

linkFormatter

({ typeName: string, jsDocTitle?: string, fullPath: string }) => string

Format function to generate link of nested types.

ignoreNestedType

When parsing nested types, whether to ignore these nested types if they are defined in some files. When returning true, nested types must not be exported, but when false is returned, nested types may not be exported due to other reasons (such as the nested type has jsdoc @title, which needs to be manually exported)

escapeChars

boolean: default to true

Whether to escape characters for extracted type text. E.g. | will be escaped to \|, <Promise> will be escaped to &lt;Promise&gt;.

Who's using?

Arco Design - A comprehensive React UI components library based on Arco Design.

LICENSE

MIT © PengJiyuan