Registry / serialization / typescript-parser

typescript-parser

library2.6.1jsnpmunverified

The `typescript-parser` package provides a utility for parsing TypeScript and JavaScript files to generate a 'human-readable' Abstract Syntax Tree (AST). It leverages the official TypeScript compiler's parsing capabilities internally. The current stable version is 2.6.1, released in August 2018. Due to the lack of activity since then, its release cadence is effectively halted. Its key differentiator lies in its promise of a more accessible AST representation compared to the raw TypeScript compiler AST, aiming to simplify consumption for tools that need to analyze code structure, such as IDE extensions or code generators. It primarily operates by parsing either source code strings or file paths, and can also build a declaration index for multiple files.

serialization

npm install typescript-parser

github ↗package ↗

INSTALL

IMPORT

SIG · TYPESCRIPT-PARSER

typescript-parser

serializationjavascriptv2.6.1

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

TypescriptParser

✓ import { TypescriptParser } from 'typescript-parser';

✗ const TypescriptParser = require('typescript-parser').TypescriptParser;

The library primarily uses ES module syntax in its documentation, but CommonJS might work for older Node.js versions. For modern TypeScript projects, use `import`.

AST declarations (e.g., ClassDeclaration)

✓ import { ClassDeclaration, PropertyDeclaration } from 'typescript-parser';

Specific AST node types are exported, allowing for type-safe manipulation of the parsed structure.

This quickstart demonstrates how to instantiate the `TypescriptParser` and use it to parse a string of TypeScript source code, then log the names of the top-level declarations and members of a specific class found in the AST.

import { TypescriptParser } from 'typescript-parser'; async function parseCode() { const parser = new TypescriptParser(); const sourceCode = ` interface MyInterface { id: string; name?: string; } export class MyClass implements MyInterface { private _id: string; public name: string; constructor(id: string, name: string) { this._id = id; this.name = name; } public get id(): string { return this._id; } public greet(): string { return `Hello, ${this.name}!`; } } `; try { const parsed = await parser.parseSource(sourceCode); console.log('Parsed declarations:', parsed.declarations.map(d => d.name)); // Example: Find the class declaration const myClass = parsed.declarations.find(d => d.name === 'MyClass'); if (myClass && 'members' in myClass) { console.log('MyClass members:', myClass.members.map((m: any) => m.name)); } } catch (error) { console.error('Error parsing source:', error); } } parseCode();

Debug

Known issues

gotchaThe package has not been updated since August 2018. This means it may not correctly parse newer TypeScript syntax features (e.g., optional chaining, nullish coalescing, private class fields, import assertions) introduced in TypeScript versions 3.x, 4.x, or 5.x.

fix

Consider alternative, actively maintained TypeScript AST parsers if working with modern TypeScript syntax, or fork and update the parsing logic to a newer TypeScript compiler version.

affects: >=2.6.1

gotchaPerformance for very large files or projects might be a concern. The library's internal parsing mechanism (recursive vs. iterative BTree Walker) has seen changes in minor versions, which could affect performance characteristics, especially in older versions.

fix

Profile performance in your specific use case. If parsing many files, consider using `parser.parseFiles` which might be optimized for batch operations, or explore other parsers if bottlenecks occur.

affects: <=2.6.1

Errors

Common errors & fixes

TypeError: Cannot read properties of undefined (reading 'length')

This error was reported in older versions due to an issue with the parser when encountering specific TypeScript constructs, especially with malformed or unexpected input.

fix

Update to at least `v2.4.0` where a fix for 'typescript error that reads length of undefined' was applied. Ensure input source code is valid TypeScript/JavaScript syntax.

Error: Cannot find module 'typescript-parser'

The `typescript-parser` package was not found in `node_modules`, likely due to incorrect installation or usage in an environment where dependencies are not properly resolved.

fix

Run `npm install typescript-parser` or `yarn add typescript-parser` in your project directory. Ensure your `node_modules` are accessible and environment variables like `NODE_PATH` are correctly configured if not using standard resolution.

Upgrade

Version history

2.6.1latest on npm

Audit

Dependencies

typescriptrequiredThis library relies on the official TypeScript compiler's internal parser. Compatibility with newer TypeScript versions beyond 2018 might be an issue.

Agent activity

18 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/TypeScript-Heroes/node-typescript-parser ↗

packagehttps://www.npmjs.com/package/typescript-parser ↗