Open Source TypeScript Static Code Analysis Tools

Graphical tool for reverse engineering of Angular projects. It allows you to navigate in the structure of your application and observe the relationship between the different modules, providers, and directives. The tool performs static code analysis which means that you don't have to run your application in order to use it. ngrev is not maintained by the Angular team. It's a side project developed by the open-source community. The application is not signed, so you may have to explicitly allow your mac to run it in System Preferences. You can add your own theme by creating a [theme-name].theme.json file in Electron [userData]/themes. For a sample theme see Dark. Your application needs to be compatible with Angular Ivy compiler. ngrev is not tested with versions older than v11. To stay up to date check the update guide on angular.io.

Extensible Angular 5+ enterprise-grade project generator based on angular-cli with best practices from the community. Bootstrap, Angular Material or even Ionic are available, just pick one and start to code. Save time and maintenance effort by creating Progressive Web App and mobile app with the same code base. The app template is based on HTML5, TypeScript and Sass. Optimized build and bundling process with Webpack. Development server with backend proxy and live reload. Cross-browser CSS with autoprefixer and browsers list. Internationalization managed by ngx-translate. Asset revisioning for better cache management. Unit tests using Jasmine, Karma, and headless Chrome. End-to-end tests using Protractor. Static code analysis: TSLint, Codelyzer, Stylelint and HTMLHint. Local knowledgebase server using Hads. Progressive Web App (PWA) support.

A set of tslint rules for static code analysis of Angular TypeScript projects. (If you are using ESLint check out the new angular-eslint repository.). You can run the static code analyzer over web apps, NativeScript, Ionic, etc. Note that by default all components are aligned with the style guide so you won't see any errors in the console. Codelyzer supports any template and style language by custom hooks. If you're using Sass for instance, you can allow codelyzer to analyze your styles by creating a file .codelyzer.js in the root of your project (where the node_modules directory is). In the configuration file can implement custom pre-processing and template resolution logic. Lint rules encode logic for syntactic & semantic checks of TypeScript, HTML, CSS and Angular expressions source code.