\n\n\n\n\n- [What is this module about](#what-is-this-module-about)\n- [Getting started](#getting-started)\n - [Install](#install)\n - [Init configuration](#init-configuration)\n- [Commands](#commands)\n - [Parse](#parse)\n - [Parse script](#parse-script)\n - [NPX](#npx)\n - [Configuration](#configuration)\n - [Stats](#stats)\n - [Stats script](#stats-script)\n - [NPX](#npx-1)\n- [Types](#types)\n- [Type detection](#type-detection)\n- [Outputs](#outputs)\n- [Contributors](#contributors)\n\n\n\n## What is this module about\n\nThis module extracts the most important information of your Angular code base and converts it into JSON. Having the most\nimportant parts of your Angular code base as JSON can be very useful to perform custom analysis or to display APIs.\nDisplaying APIs is especially useful for library authors that want to illustrate their library in a component showcase.\n\n## Getting started\n\n### Install\n\nInstall ng-parsel as a dev dependency in your repository.\n\n```bash\nnpm i -D @angular-experts/ng-parsel\n```\n\n### Init configuration\n\nOnce installed you can use npx to create an initial configuration for ng-parsel.\n\n```bash\nnpx @angular-experts/ng-parsel init\n```\n\nRunning this command will create a `.parselrc.json` configuration file in the root of your repository. Check the initial\nconfiguration and adjust if needed. The configuration properties and their meaning are explained in\nthe [configuration section](#configuration).\n\n## Commands\n\n### Parse\n\nTo parse the code base you can either create a parse script in your `package.json`which calls `ng-parsel` or you can use\nnpx.\n\n#### Parse script\n\nAdd the following script to your `package.json`.\n\n```json\n\"parse\": \"@angular-experts/ng-parsel parse\"\n```\n\nOnce added, you can open up a terminal and run the following command.\n\n```bash\nnpm run parse\n```\n\n#### NPX\n\nTo parse your code base with npx you can run the follwoing command inisde a terminal of your choice.\n\n```bash\nnpx @angular-experts/ng-parsel parse\n```\n\n#### Configuration\n\nng-parsel offers the following configurations.\n\n| Property | Default value | Description |\n| --------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |\n| src | 'src' | Glob to query all the src files that should be parsed |\n| out | 'ng-parsel' | Output directory |\n| parseComponents | true | If set to `true` ng-parsel will parse Angular Components and include them in the output. |\n| parseServices | true | If set to `true` ng-parsel will parse Angular Services and include them in the output. |\n| parsePipes | true | If set to `true` ng-parsel will parse Angular Pipes and include them in the output. |\n| parseDirectives | true | If set to `true` ng-parsel will parse Angular Directives and include them in the output. |\n| parseModules | true | If set to true ng-parsel will parse Angular Modules and include them in the output. |\n| parseHarnesses | true | If set to true ng-parsel will parse Harness test files (all files ending with `.harness.ts`) and include them in the output. |\n| parseValidators | true | If set to true ng-parsel will parse Validators (all files ending with `.validator.ts`) and include them in the output. |\n| parseSpecs | true | If set to true ng-parsel will parse testing files (all files ending with `.spec.ts`) and include them in the output. |\n| singleFile | true | If set to to `true` the output will be written to a `ng-parsel.json` file in the output directory. If set to false, ng-parsel will generate multiple output files, one for each `componentType`. (Find out more on component types in the [next section](#component-type)) |\n\n### Stats\n\nThe stats command is a command that gives you a quick overview of your Angular application. It shows you how many components, services, pipes, directives, modules, harnesses and specs you have in your application. Furthermore, it shows you interesting insights, like how many are standanlone and how many are part of a module.\nTo run the stats command you can either create a stats script in your `package.json`which calls `ng-parsel` or you can use `npx`;\n\n#### Stats script\n\n```json\n\"stats\": \"@angular-experts/ng-parsel stats\"\n```\n\n#### NPX\n\n```bash\nnpx @angular-experts/ng-parsel stats\n```\n\n## Types\n\nCurrently ng-parsel classifies each file into one of the following `NgParselOutputType`.\n\n- Component\n- Service\n- Pipes\n- Modules\n- Directives\n- Harnesses\n- Specs\n- Unknown\n\nUnknown files will not be parsed. If you need support for additional types please raise an issue or open a PR.\n\n## Type detection\n\nHarnesses, Specs and Validators are detected by the filename. Everything that ends with `.spec` will be classified\nas a spec file. Everything that ends with `.harness` will be classified as a harness file. Everything that ends with\n`.validator` will be classified as a validator file.\n\nAll other types are detected by their Angular decorators.\n\n## Outputs\n\nSingle outputs will be written to a `ng-parsel.json` file in the output directory.\nIf `singleFile` is set to `false` ng-parsel will generate multiple output files, one for each `componentType`. (Find out more on [component types](#component-type))\n\n## Contributors\n\n\n\n\n
![](\"https://github.com/angular-experts-io/ng-parsel/blob/main/docs/logo.png?raw=true\"){kind=logo}
\n![\"Kevin](\"https://avatars.githubusercontent.com/u/5468954?v=4?s=100\")
![\"@NgDaddy\"/](\"https://avatars.githubusercontent.com/u/81327266?v=4?s=100\")
![\"Ilir](\"https://avatars.githubusercontent.com/u/24731032?v=4?s=100\")
![\"Quentin\"/](\"https://avatars.githubusercontent.com/u/9989211?v=4?s=100\")