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

@angular-experts/ng-parsel

v3.3.0

Published

Tool that transforms Angular codebase to JSON representation

Downloads

177

Readme

ng-parsel

All Contributors

Coverage Status

Convert your Angular components to JSON

ng-parsel logo

What is this module about

This module extracts the most important information of your Angular code base and converts it into JSON. Having the most important parts of your Angular code base as JSON can be very useful to perform custom analysis or to display APIs. Displaying APIs is especially useful for library authors that want to illustrate their library in a component showcase.

Getting started

Install

Install ng-parsel as a dev dependency in your repository.

npm i -D @angular-experts/ng-parsel

Init configuration

Once installed you can use npx to create an initial configuration for ng-parsel.

npx @angular-experts/ng-parsel init

Running this command will create a .parselrc.json configuration file in the root of your repository. Check the initial configuration and adjust if needed. The configuration properties and their meaning are explained in the configuration section.

Parse codebase

To parse the code base you can either create a parse script in your package.jsonwhich calls ng-parsel or you can use npx.

Parse script

Add the following script to your package.json.

"parse": "@angular-experts/ng-parsel parse"

Once added, you can open up a terminal and run the following command.

npm run parse

NPX

To parse your code base with npx you can run the follwoing command inisde a terminal of your choice.

npx @angular-experts/ng-parsel parse

Configuration

ng-parsel offers the following configurations.

| Property | Default value | Description | | --------------- | ------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | src | 'src' | Glob to query all the src files that should be parsed | | out | 'ng-parsel' | Output directory | | parseComponents | true | If set to true ng-parsel will parse Angular Components and include them in the output. | | parseServices | true | If set to true ng-parsel will parse Angular Services and include them in the output. | | parsePipes | true | If set to true ng-parsel will parse Angular Pipes and include them in the output. | | parseDirectives | true | If set to true ng-parsel will parse Angular Directives and include them in the output. | | parseModules | true | If set to true ng-parsel will parse Angular Modules and include them in the output. | | 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. | | parseValidators | true | If set to true ng-parsel will parse Validators (all files ending with .validtor.ts) and include them in the output. | | parseSpecs | true | If set to true ng-parsel will parse testing files (all files ending with .spec.ts) and include them in the output. | | 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) |

Types

Currently ng-parsel classifies each file into one of the following NgParselOutputType.

  • Component
  • Service
  • Pipes
  • Modules
  • Directives
  • Harnesses
  • Specs
  • Unknown

Unknown files will not be parsed. If you need support for additional types please raise an issue or open a PR.

Type detection

Harnesses, Specs and Validators are detected by the filename. Everything that ends with .spec will be classified as a spec file. Everything that ends with .harness will be classified as a harness file. Everything that ends with .validator will be classified as a validator file.

All other types are detected by their Angular decorators.

Outputs

Single outputs will be written to a ng-parsel.json file in the output directory. If singleFile is set to false ng-parsel will generate multiple output files, one for each componentType. (Find out more on component types)

Contributors