Command line tool to generate Angular Components and Directives
- Put the templates in as multiline strings so it comes along with the executable
- Put the template directory in the bin folder
- Initial version
Use this package as an executable
1. Install it
You can install the package from the command line:
$ pub global activate ngen
2. Use it
The package has the following executables:
Use this package as a library
1. Depend on it
Add this to your package's pubspec.yaml file:
dependencies: ngen: ^0.0.1+2
2. Install it
You can install packages from the command line:
$ pub get
$ flutter pub get
Alternatively, your editor might support
pub get or
flutter pub get.
Check the docs for your editor to learn more.
3. Import it
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Dec 9, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
- Dart: 2.6.1
- pana: 0.12.21
lib/generator/component_generator.dart. (-1 points)
lib/generator/component_generator.dart reported 2 hints:
line 12 col 23: Unnecessary new keyword.
line 26 col 21: Unnecessary new keyword.
lib/ngen.dart. (-1 points)
lib/ngen.dart reported 2 hints:
line 1 col 8: Unused import: 'package:args/args.dart'.
line 12 col 20: Unnecessary new keyword.
lib/commands/create_command.dart. (-0.50 points)
lib/commands/create_command.dart reported 1 hint:
line 12 col 24: Unnecessary new keyword.
dartfmt to format
dartfmt to format
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
ngen.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
Package is pre-v0.1 release. (-10 points)
While nothing is inherently wrong with versions of
0.0.*, it might mean that the author is still experimenting with the general direction of the API.
The package description is too short. (-6 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.