Package Exports

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (ngx-spec) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

ngx-spec

A missing schematic for creating Angular spec.

Works only from @angular/cli@^6.0.0 on.

Installation

Angular 7+:

npm i -D ngx-spec@^2.0.0

Angular 6 (only spec, no specs support):

npm i -D ngx-spec@^1.0.0

Supported types

Supported types are

const SupportedTypes = ['component', 'directive', 'guard', 'service', 'pipe'];

ng g ngx:spec

Run:

ng g ngx-spec:spec path/my.service

ng g ngx-spec:spec path/my.service.ts

Please note that in a standard Angular CLI project the path will start at src/app. That's why if you use the file paths then it would be comfortable to cd src/app first and then safely use the shell autocompletion to produce the proper path.

ng g ngx-spec:specs

Batch specs generator. Supports minimatch globs. Does not override existing spec files.

Important: the glob should be passed as a string, otherwise OS tries to intercept it with its glob.

Examples:

ng g ngx-spec:specs 'path/*.service.ts'

ng g ngx-spec:specs '**/*.service.ts'

ng g ngx-spec:specs '**/*'

etc.

Please note that in a standard Angular CLI project the path will start at src/app. That's why if you use the file paths then it would be comfortable to cd src/app first and then safely use the shell autocompletion to produce the proper path.

Usage in Visual Studio Code

It could be easier to use the schematic with vscode-angular-schematics extension in Visual Studio Code.

History

See the story behind on stackoverflow and on Angular CLI github issue.

License

MIT