kristianmandrup / typescript-ast-processor

Process a TypeScript AST using visitors, collectors and instrumentation

Quick AST (QAST)

QAST is designed as a foundation for writing tools that work with the TypeScript AST. It aims to provide a higher level API, query engine, node data aggregators etc.

QAST should alleviate much of the pain when working with the AST directly. It lets you work at a higher abstraction level than with the "bare metal" AST, while still making it available when necessary.

Also see additional docs

Mono repo

QAST is currently structured as a mono repo, using lerna with yarn workspaces

Lerna packages

• core
• traverser
• visitor
• instrumentor
• node
• node-matcher
• node-details
• node-types
• query
• service
• utils
• loggable
• test-utils

Disclaimer

Please help contribute to make it happen, see Contributing

Resources

• TypeScript: Using-the-Compiler-API

See Resources for more

Testing

See Testing

Tool integration

We will try to make it easy to integrate other tools, so that this design is intent bases without making assumptions about underlying use or implementation.

For more see Tool integration

Customization

You should be able to use tsutils to make it easier to gather information and work with the underlying typescript AST.

ESLint traverser

We intend to extend astravel to have a similar API and design if this turns out to be as awesome as we think it could be...

Author

Kristian Mandrup

License

MIT

typescript-ast-processor's Issues

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.