前段时间一直在研究ts编译器的api,期望做一些有趣的事情,可惜最终发现api不能支持实现我的想法(提了issues,但是没有被接受),但是在翻阅资料的时候发现了这篇官方wiki,虽然还是发现有很多资料缺少,但是简单看了之后,我确实使用这篇文章中的示例找到了一些方案来调用api,修改ast,所以决定将它简单翻译一下,发表出来
下面是译文正文
免责声明
请记住,这还不是一个稳定的 API - 我们将其作为 0.5 版发布,随着时间的推移,情况会发生变化。作为第一次迭代,会有一些粗糙的边缘。我们鼓励来自社区的任何和所有反馈以改进 API。为了允许用户在未来版本之间转换,我们将记录每个新版本的任何 [API Breaking Changes]。
开始设置
首先,您需要从 npm 安装 TypeScript >=1.6。
完成后,您需要从项目所在的任何位置链接它。 如果您不在 Node 项目内进行链接,它将只是全局链接。
npm install -g typescript
npm link typescript
对于其中一些示例,您还需要 Node.js 声明文件。 要获取声明文件,请运行:
npm install -D @types/node
就是这样,你准备好了。现在您可以尝试以下一些示例。
编译器 API 有几个主要组件:
- 一个“程序”,它是整个应用程序的 TypeScript 术语
- 一个代表用户系统的
CompilerHost,带有用于读取文件、检查目录和区分大小写等的API。 - 许多
SourceFile代表应用程序中的每个源文件,管理源码和TypeScript AST
一个最小的编译器
这个例子是一个准系统编译器,它接受一个 TypeScript 文件列表并将它们编译成相应的 JavaScript。
我们需要通过createProgram创建一个Program——这将创建一个默认的CompilerHost,它使用文件系统来获取文件。
import * as ts from "typescript";
function compile(fileNames: string[], options: ts.CompilerOptions): void {
let program = ts.createProgram(fileNames, options);
let emitResult = program.emit();
let allDiagnostics = ts
.getPreEmitDiagnostics(program)
.concat(emitResult.diagnostics);
allDiagnostics.forEach(diagnostic => {
if (diagnostic.file) {
let { line, character } = ts.getLineAndCharacterOfPosition(diagnostic.file, diagnostic.start!);
let message = ts.flattenDiagnosticMessageText(diagnostic.messageText, "\n");
console.log(`${diagnostic.file.fileName} (${line + 1},${character + 1}): ${message}`);
} else {
console.log(ts.flattenDiagnosticMessageText(diagnostic.messageText, "\n"));
}
});
let exitCode = emitResult.emitSkipped ? 1 : 0;
console.log(`Process exiting with code '${exitCode}'.`);
process.exit(exitCode);
}
compile(process.argv.slice(2), {
noEmitOnError: true,
noImplicitAny: true,
target: ts.ScriptTarget.ES5,
module: ts.ModuleKind.CommonJS
});
一个简单的变换函数
创建一个编译器不需要太多代码行,但您可能只想获得给定 TypeScript 源码的相应 JavaScript 输出。
为此,您可以使用 ts.transpileModule 在两行中获取string => string转换。
import * as ts from "typescript";
const source = "let x: string = 'string'";
let result = ts.transpileModule(source, { compilerOptions: { module: ts.ModuleKind.CommonJS }});
console.log(JSON.stringify(result));
从 JavaScript 文件中获取 DTS
这仅适用于 TypeScript 3.7 及更高版本。此示例展示了如何获取 JavaScript 文件列表,并将在终端中显示它们生成的 d.ts 文件。
import * as ts from "typescript";
function compile(fileNames: string[], options: ts.CompilerOptions): void {
// Create a Program with an in-memory emit
const createdFiles = {}
const host = ts.createCompilerHost(options);
host.writeFile = (fileName: string, contents: string) => createdFiles[fileName] = contents
// Prepare and emit the d.ts files
const program = ts.createProgram(fileNames, options, host);
program.emit();
// Loop through all the input files
fileNames.forEach(file => {
console.log("### JavaScript\n")
console.log(host.readFile(file))
console.log("### Type Definition\n")
const dts = file.replace(".js", ".d.ts")
console.log(createdFiles[dts])
})
}
// Run the compiler
compile(process.argv.slice(2), {
allowJs: true,
declaration: true,
emitDeclarationOnly: true,
});
重新打印 TypeScript 文件的部分
此示例将注销 TypeScript 或 JavaScript 源文件的子部分,此模式在您需要时很有用 您的应用程序的代码是事实的来源。例如通过他们的 JSDoc 评论展示导出。
import * as ts from "typescript";
/**
* Prints out particular nodes from a source file
*
* @param file a path to a file
* @param identifiers top level identifiers available
*/
function extract(file: string, identifiers: string[]): void {
// Create a Program to represent the project, then pull out the
// source file to parse its AST.
let program = ts.createProgram([file], { allowJs: true });
const sourceFile = program.getSourceFile(file);
// To print the AST, we'll use TypeScript's printer
const printer = ts.createPrinter({ newLine: ts.NewLineKind.LineFeed });
// To give constructive error messages, keep track of found and un-found identifiers
const unfoundNodes = [], foundNodes = [];
// Loop through the root AST nodes of the file
ts.forEachChild(sourceFile, node => {
let name = "";
// This is an incomplete set of AST nodes which could have a top level identifier
// it's left to you to expand this list, which you can do by using
// https://ts-ast-viewer.com/ to see the AST of a file then use the same patterns
// as below
if (ts.isFunctionDeclaration(node)) {
name = node.name.text;
// Hide the method body when printing
node.body = undefined;
} else if (ts.isVariableStatement(node)) {
name = node.declarationList.declarations[0].name.getText(sourceFile);
} else if (ts.isInterfaceDeclaration(node)){
name = node.name.text
}
const container = identifiers.includes(name) ? foundNodes : unfoundNodes;
container.push([name, node]);
});
// Either print the found nodes, or offer a list of what identifiers were found
if (!foundNodes.length) {
console.log(`Could not find any of ${identifiers.join(", ")} in ${file}, found: ${unfoundNodes.filter(f => f[0]).map(f => f[0]).join(", ")}.`);
process.exitCode = 1;
} else {
foundNodes.map(f => {
const [name, node] = f;
console.log("### " + name + "\n");
console.log(printer.printNode(ts.EmitHint.Unspecified, node, sourceFile)) + "\n";
});
}
}
// Run the extract function with the script's arguments
extract(process.argv[2], process.argv.slice(3));
用little linter遍历 AST
Node 接口是 TypeScript AST 的根接口。通常,我们以递归方式使用 forEachChild 函数来遍历树。这包含了访问者模式并且通常提供更多的灵活性。
作为如何遍历文件的 AST 的示例,请考虑执行以下操作的最小 linter:
- 检查所有循环构造体是否被花括号括起来。
- 检查所有 if/else 主体是否被花括号括起来。
- 使用“更严格”的相等运算符(
===/!==)代替“松散”的(==/!=)。
import { readFileSync } from "fs";
import * as ts from "typescript";
export function delint(sourceFile: ts.SourceFile) {
delintNode(sourceFile);
function delintNode(node: ts.Node) {
switch (node.kind) {
case ts.SyntaxKind.ForStatement:
case ts.SyntaxKind.ForInStatement:
case ts.SyntaxKind.WhileStatement:
case ts.SyntaxKind.DoStatement:
if ((node as ts.IterationStatement).statement.kind !== ts.SyntaxKind.Block) {
report(
node,
'A looping statement\'s contents should be wrapped in a block body.'
);
}
break;
case ts.SyntaxKind.IfStatement:
const ifStatement = node as ts.IfStatement;
if (ifStatement.thenStatement.kind !== ts.SyntaxKind.Block) {
report(ifStatement.thenStatement, 'An if statement\'s contents should be wrapped in a block body.');
}
if (
ifStatement.elseStatement &&
ifStatement.elseStatement.kind !== ts.SyntaxKind.Block &&
ifStatement.elseStatement.kind !== ts.SyntaxKind.IfStatement
) {
report(
ifStatement.elseStatement,
'An else statement\'s contents should be wrapped in a block body.'
);
}
break;
case ts.SyntaxKind.BinaryExpression:
const op = (node as ts.BinaryExpression).operatorToken.kind;
if (op === ts.SyntaxKind.EqualsEqualsToken || op === ts.SyntaxKind.ExclamationEqualsToken) {
report(node, 'Use \'===\' and \'!==\'.');
}
break;
}
ts.forEachChild(node, delintNode);
}
function report(node: ts.Node, message: string) {
const { line, character } = sourceFile.getLineAndCharacterOfPosition(node.getStart());
console.log(`${sourceFile.fileName} (${line + 1},${character + 1}): ${message}`);
}
}
const fileNames = process.argv.slice(2);
fileNames.forEach(fileName => {
// Parse a file
const sourceFile = ts.createSourceFile(
fileName,
readFileSync(fileName).toString(),
ts.ScriptTarget.ES2015,
/*setParentNodes */ true
);
// delint it
delint(sourceFile);
});
在这个例子中,我们不需要创建类型检查器,因为我们想要做的只是遍历每个 SourceFile。
所有可能的 ts.SyntaxKind 都可以在 enum 这里下找到。
编写增量程序观察器
TypeScript 2.7 引入了两个新 API:一个用于创建提供一组 API 以触发重建的“观察者”程序,以及观察者可以利用的“构建器”API。
BuilderProgram 是 Program 实例,它们足够智能,可以缓存错误,并在之前编译的模块或它们的依赖项没有以级联方式更新的情况下在模块上发出。
观察者可以利用构建器程序实例仅更新编译中受影响文件的结果(如错误和发出)。
这可以加速包含许多文件的大型项目。
该 API 在编译器内部用于实现其 --watch 模式,但也可以被其他工具利用,如下所示:
import ts = require("typescript");
const formatHost: ts.FormatDiagnosticsHost = {
getCanonicalFileName: path => path,
getCurrentDirectory: ts.sys.getCurrentDirectory,
getNewLine: () => ts.sys.newLine
};
function watchMain() {
const configPath = ts.findConfigFile(
/*searchPath*/ "./",
ts.sys.fileExists,
"tsconfig.json"
);
if (!configPath) {
throw new Error("Could not find a valid 'tsconfig.json'.");
}
// TypeScript can use several different program creation "strategies":
// * ts.createEmitAndSemanticDiagnosticsBuilderProgram,
// * ts.createSemanticDiagnosticsBuilderProgram
// * ts.createAbstractBuilder
// The first two produce "builder programs". These use an incremental strategy
// to only re-check and emit files whose contents may have changed, or whose
// dependencies may have changes which may impact change the result of prior
// type-check and emit.
// The last uses an ordinary program which does a full type check after every
// change.
// Between `createEmitAndSemanticDiagnosticsBuilderProgram` and
// `createSemanticDiagnosticsBuilderProgram`, the only difference is emit.
// For pure type-checking scenarios, or when another tool/process handles emit,
// using `createSemanticDiagnosticsBuilderProgram` may be more desirable.
const createProgram = ts.createSemanticDiagnosticsBuilderProgram;
// Note that there is another overload for `createWatchCompilerHost` that takes
// a set of root files.
const host = ts.createWatchCompilerHost(
configPath,
{},
ts.sys,
createProgram,
reportDiagnostic,
reportWatchStatusChanged
);
// You can technically override any given hook on the host, though you probably
// don't need to.
// Note that we're assuming `origCreateProgram` and `origPostProgramCreate`
// doesn't use `this` at all.
const origCreateProgram = host.createProgram;
host.createProgram = (rootNames: ReadonlyArray<string>, options, host, oldProgram) => {
console.log("** We're about to create the program! **");
return origCreateProgram(rootNames, options, host, oldProgram);
};
const origPostProgramCreate = host.afterProgramCreate;
host.afterProgramCreate = program => {
console.log("** We finished making the program! **");
origPostProgramCreate!(program);
};
// `createWatchProgram` creates an initial program, watches files, and updates
// the program over time.
ts.createWatchProgram(host);
}
function reportDiagnostic(diagnostic: ts.Diagnostic) {
console.error("Error", diagnostic.code, ":", ts.flattenDiagnosticMessageText( diagnostic.messageText, formatHost.getNewLine()));
}
/**
* Prints a diagnostic every time the watch status changes.
* This is mainly for messages like "Starting compilation" or "Compilation completed".
*/
function reportWatchStatusChanged(diagnostic: ts.Diagnostic) {
console.info(ts.formatDiagnostic(diagnostic, formatHost));
}
watchMain();
使用语言服务的增量构建支持
请参阅[Using the Language Service API]页面了解更多详情。
服务层提供了一组额外的实用程序,可以帮助简化一些复杂的场景。在下面的代码片段中,我们将尝试构建一个增量构建服务器,该服务器监视一组文件并仅更新更改的文件的输出。
我们将通过创建 LanguageService 对象来实现这一点。与前面示例中的程序类似,我们需要一个 LanguageServiceHost。 LanguageServiceHost 通过version、isOpen 标志和ScriptSnapshot 增强了文件的概念。 version 允许语言服务跟踪对文件的更改。 isOpen 告诉语言服务在文件使用时将 AST 保留在内存中。 ScriptSnapshot 是对文本的抽象,允许语言服务查询更改。
如果您只是想实现 watch 风格的功能,我们鼓励您探索上述 watcher API。
import * as fs from "fs";
import * as ts from "typescript";
function watch(rootFileNames: string[], options: ts.CompilerOptions) {
const files: ts.MapLike<{ version: number }> = {};
// initialize the list of files
rootFileNames.forEach(fileName => {
files[fileName] = { version: 0 };
});
// Create the language service host to allow the LS to communicate with the host
const servicesHost: ts.LanguageServiceHost = {
getScriptFileNames: () => rootFileNames,
getScriptVersion: fileName =>
files[fileName] && files[fileName].version.toString(),
getScriptSnapshot: fileName => {
if (!fs.existsSync(fileName)) {
return undefined;
}
return ts.ScriptSnapshot.fromString(fs.readFileSync(fileName).toString());
},
getCurrentDirectory: () => process.cwd(),
getCompilationSettings: () => options,
getDefaultLibFileName: options => ts.getDefaultLibFilePath(options),
fileExists: ts.sys.fileExists,
readFile: ts.sys.readFile,
readDirectory: ts.sys.readDirectory,
directoryExists: ts.sys.directoryExists,
getDirectories: ts.sys.getDirectories,
};
// Create the language service files
const services = ts.createLanguageService(servicesHost, ts.createDocumentRegistry());
// Now let's watch the files
rootFileNames.forEach(fileName => {
// First time around, emit all files
emitFile(fileName);
// Add a watch on the file to handle next change
fs.watchFile(fileName, { persistent: true, interval: 250 }, (curr, prev) => {
// Check timestamp
if (+curr.mtime <= +prev.mtime) {
return;
}
// Update the version to signal a change in the file
files[fileName].version++;
// write the changes to disk
emitFile(fileName);
});
});
function emitFile(fileName: string) {
let output = services.getEmitOutput(fileName);
if (!output.emitSkipped) {
console.log(`Emitting ${fileName}`);
} else {
console.log(`Emitting ${fileName} failed`);
logErrors(fileName);
}
output.outputFiles.forEach(o => {
fs.writeFileSync(o.name, o.text, "utf8");
});
}
function logErrors(fileName: string) {
let allDiagnostics = services
.getCompilerOptionsDiagnostics()
.concat(services.getSyntacticDiagnostics(fileName))
.concat(services.getSemanticDiagnostics(fileName));
allDiagnostics.forEach(diagnostic => {
let message = ts.flattenDiagnosticMessageText(diagnostic.messageText, "\n");
if (diagnostic.file) {
let { line, character } = diagnostic.file.getLineAndCharacterOfPosition(
diagnostic.start!
);
console.log(` Error ${diagnostic.file.fileName} (${line + 1},${character +1}): ${message}`);
} else {
console.log(` Error: ${message}`);
}
});
}
}
// Initialize files constituting the program as all .ts files in the current directory
const currentDirectoryFiles = fs
.readdirSync(process.cwd())
.filter(fileName => fileName.length >= 3 && fileName.substr(fileName.length - 3, 3) === ".ts");
// Start the watcher
watch(currentDirectoryFiles, { module: ts.ModuleKind.CommonJS });
自定义模块分辨率
您可以通过实现可选方法来覆盖编译器解析模块的标准方式:CompilerHost.resolveModuleNames:
CompilerHost.resolveModuleNames(moduleNames: string[], containsFile: string): string[]。
该方法被赋予一个文件中的模块名称列表,并期望返回一个大小为moduleNames.length的数组,该数组的每个元素存储:
- 一个具有非空属性的
ResolvedModule实例resolvedFileName- 解析来自moduleNames数组的相应名称或 undefined如果模块名称无法解析。
您可以通过调用 resolveModuleName 来调用标准模块解析过程:
resolveModuleName(moduleName: string, containsFile: string, options: CompilerOptions, moduleResolutionHost: ModuleResolutionHost): ResolvedModuleNameWithFallbackLocations。
此函数返回一个对象,该对象存储模块解析的结果(resolvedModule 属性的值)以及在做出当前决策之前被视为候选的文件名列表。
import * as ts from "typescript";
import * as path from "path";
function createCompilerHost(options: ts.CompilerOptions, moduleSearchLocations: string[]): ts.CompilerHost {
return {
getSourceFile,
getDefaultLibFileName: () => "lib.d.ts",
writeFile: (fileName, content) => ts.sys.writeFile(fileName, content),
getCurrentDirectory: () => ts.sys.getCurrentDirectory(),
getDirectories: path => ts.sys.getDirectories(path),
getCanonicalFileName: fileName =>
ts.sys.useCaseSensitiveFileNames ? fileName : fileName.toLowerCase(),
getNewLine: () => ts.sys.newLine,
useCaseSensitiveFileNames: () => ts.sys.useCaseSensitiveFileNames,
fileExists,
readFile,
resolveModuleNames
};
function fileExists(fileName: string): boolean {
return ts.sys.fileExists(fileName);
}
function readFile(fileName: string): string | undefined {
return ts.sys.readFile(fileName);
}
function getSourceFile(fileName: string, languageVersion: ts.ScriptTarget, onError?: (message: string) => void) {
const sourceText = ts.sys.readFile(fileName);
return sourceText !== undefined
? ts.createSourceFile(fileName, sourceText, languageVersion)
: undefined;
}
function resolveModuleNames(
moduleNames: string[],
containingFile: string
): ts.ResolvedModule[] {
const resolvedModules: ts.ResolvedModule[] = [];
for (const moduleName of moduleNames) {
// try to use standard resolution
let result = ts.resolveModuleName(moduleName, containingFile, options, {
fileExists,
readFile
});
if (result.resolvedModule) {
resolvedModules.push(result.resolvedModule);
} else {
// check fallback locations, for simplicity assume that module at location
// should be represented by '.d.ts' file
for (const location of moduleSearchLocations) {
const modulePath = path.join(location, moduleName + ".d.ts");
if (fileExists(modulePath)) {
resolvedModules.push({ resolvedFileName: modulePath });
}
}
}
}
return resolvedModules;
}
}
function compile(sourceFiles: string[], moduleSearchLocations: string[]): void {
const options: ts.CompilerOptions = {
module: ts.ModuleKind.AMD,
target: ts.ScriptTarget.ES5
};
const host = createCompilerHost(options, moduleSearchLocations);
const program = ts.createProgram(sourceFiles, options, host);
/// do something with program...
}
创建和打印 TypeScript AST
TypeScript 具有工厂(factory)函数和可以结合使用的printer API。
- 工厂允许您以 TypeScript 的 AST 格式生成新的树节点。
- printer可以采用现有的树(由
createSourceFile或工厂(factory)函数生成的树),并生成输出字符串。
这是一个利用两者来生成阶乘函数的示例:
import ts = require("typescript");
function makeFactorialFunction() {
const functionName = ts.factory.createIdentifier("factorial");
const paramName = ts.factory.createIdentifier("n");
const parameter = ts.factory.createParameterDeclaration(
/*decorators*/ undefined,
/*modifiers*/ undefined,
/*dotDotDotToken*/ undefined,
paramName
);
const condition = ts.factory.createBinaryExpression(paramName, ts.SyntaxKind.LessThanEqualsToken, ts.factory.createNumericLiteral(1));
const ifBody = ts.factory.createBlock([ts.factory.createReturnStatement(ts.factory.createNumericLiteral(1))], /*multiline*/ true);
const decrementedArg = ts.factory.createBinaryExpression(paramName, ts.SyntaxKind.MinusToken, ts.factory.createNumericLiteral(1));
const recurse = ts.factory.createBinaryExpression(paramName, ts.SyntaxKind.AsteriskToken, ts.factory.createCallExpression(functionName, /*typeArgs*/ undefined, [decrementedArg]));
const statements = [ts.factory.createIfStatement(condition, ifBody), ts.factory.createReturnStatement(recurse)];
return ts.factory.createFunctionDeclaration(
/*decorators*/ undefined,
/*modifiers*/ [ts.factory.createToken(ts.SyntaxKind.ExportKeyword)],
/*asteriskToken*/ undefined,
functionName,
/*typeParameters*/ undefined,
[parameter],
/*returnType*/ ts.factory.createKeywordTypeNode(ts.SyntaxKind.NumberKeyword),
ts.factory.createBlock(statements, /*multiline*/ true)
);
}
const resultFile = ts.createSourceFile("someFileName.ts", "", ts.ScriptTarget.Latest, /*setParentNodes*/ false, ts.ScriptKind.TS);
const printer = ts.createPrinter({ newLine: ts.NewLineKind.LineFeed });
const result = printer.printNode(ts.EmitHint.Unspecified, makeFactorialFunction(), resultFile);
console.log(result);
使用类型检查器
在这个例子中,我们将遍历 AST 并使用检查器(checker)来序列化类信息。 我们将使用类型检查器来获取符号和类型信息,同时为导出的类、它们的构造函数和各自的构造函数参数获取 JSDoc 注释。
import * as ts from "typescript";
import * as fs from "fs";
interface DocEntry {
name?: string;
fileName?: string;
documentation?: string;
type?: string;
constructors?: DocEntry[];
parameters?: DocEntry[];
returnType?: string;
}
/** Generate documentation for all classes in a set of .ts files */
function generateDocumentation(
fileNames: string[],
options: ts.CompilerOptions
): void {
// Build a program using the set of root file names in fileNames
let program = ts.createProgram(fileNames, options);
// Get the checker, we will use it to find more about classes
let checker = program.getTypeChecker();
let output: DocEntry[] = [];
// Visit every sourceFile in the program
for (const sourceFile of program.getSourceFiles()) {
if (!sourceFile.isDeclarationFile) {
// Walk the tree to search for classes
ts.forEachChild(sourceFile, visit);
}
}
// print out the doc
fs.writeFileSync("classes.json", JSON.stringify(output, undefined, 4));
return;
/** visit nodes finding exported classes */
function visit(node: ts.Node) {
// Only consider exported nodes
if (!isNodeExported(node)) {
return;
}
if (ts.isClassDeclaration(node) && node.name) {
// This is a top level class, get its symbol
let symbol = checker.getSymbolAtLocation(node.name);
if (symbol) {
output.push(serializeClass(symbol));
}
// No need to walk any further, class expressions/inner declarations
// cannot be exported
} else if (ts.isModuleDeclaration(node)) {
// This is a namespace, visit its children
ts.forEachChild(node, visit);
}
}
/** Serialize a symbol into a json object */
function serializeSymbol(symbol: ts.Symbol): DocEntry {
return {
name: symbol.getName(),
documentation: ts.displayPartsToString(symbol.getDocumentationComment(checker)),
type: checker.typeToString(
checker.getTypeOfSymbolAtLocation(symbol, symbol.valueDeclaration!)
)
};
}
/** Serialize a class symbol information */
function serializeClass(symbol: ts.Symbol) {
let details = serializeSymbol(symbol);
// Get the construct signatures
let constructorType = checker.getTypeOfSymbolAtLocation(
symbol,
symbol.valueDeclaration!
);
details.constructors = constructorType
.getConstructSignatures()
.map(serializeSignature);
return details;
}
/** Serialize a signature (call or construct) */
function serializeSignature(signature: ts.Signature) {
return {
parameters: signature.parameters.map(serializeSymbol),
returnType: checker.typeToString(signature.getReturnType()),
documentation: ts.displayPartsToString(signature.getDocumentationComment(checker))
};
}
/** True if this is visible outside this file, false otherwise */
function isNodeExported(node: ts.Node): boolean {
return (
(ts.getCombinedModifierFlags(node as ts.Declaration) & ts.ModifierFlags.Export) !== 0 ||
(!!node.parent && node.parent.kind === ts.SyntaxKind.SourceFile)
);
}
}
generateDocumentation(process.argv.slice(2), {
target: ts.ScriptTarget.ES5,
module: ts.ModuleKind.CommonJS
});
试试这个:
tsc docGenerator.ts --m commonjs
node docGenerator.js test.ts
传递如下输入:
/**
* Documentation for C
*/
class C {
/**
* constructor documentation
* @param a my parameter documentation
* @param b another parameter documentation
*/
constructor(a: string, b: C) { }
}
我们应该得到如下输出:
[
{
"name": "C",
"documentation": "Documentation for C ",
"type": "typeof C",
"constructors": [
{
"parameters": [
{
"name": "a",
"documentation": "my parameter documentation",
"type": "string"
},
{
"name": "b",
"documentation": "another parameter documentation",
"type": "C"
}
],
"returnType": "C",
"documentation": "constructor documentation"
}
]
}
]
译者话:翻看文档最好的方式当然还是看官方的原版文档,这篇译文只是一个简单的翻译,并且不保证实时更新,本文翻译使用谷歌翻译作为粗翻,在人工简单修改,话说谷歌翻译真的好用。
本文翻译按照只译叙述性文本,不译代码的原则进行