Libraries generated by cli using ng generate library creates a subproject using Karma intead of Jest
#1
Comments
|
Thanks for moving this issue over. So you're talking about and Angular CLI library not an Nx library correct? |
|
Yes. NG CLI only. |
|
I'll look into this. |
schuchard
added a commit
that referenced
this issue
Sep 2, 2020
Add support single application projects and workspaces with apps and libraries. ## Jest runner Replace the direct reliance on [`jest-preset-angular`](https://github.com/thymikee/jest-preset-angular) and package json scripts in favor of [`angular-builders/jest`](https://github.com/just-jeb/angular-builders/tree/master/packages/jest). This provides the ability to run tests with `ng test` This should address #30 #28 #22 #11 It better positions us to support #1 ## Jest types Update each projects `tsconfig.spec.json` to configure the `jest` types while removing `jasmine` This should address #24 #14 ## Other Non-user facing changes - refactor development scripts from `package.json` to TS file - create 2 sandboxes (single app and workspace with app and lib) - test both sandboxes during CI - add MIT license - add prettier
|
Is this resolved? |
|
This feature has not been built. Generating code with the CLI will still use the defaults. However, this schematic is in a better position to offer this functionality in the future. |
|
Is there any options except for the Nx? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reopen from briebug/jest#9.
At first it was a bug report... now I think it is a feature request
Is your feature request related to a problem? Please describe.
After using this schematics to convert my project into a Jest one, I expected all libs I created to also be Jest projects.
Describe the solution you'd like
After running all the steps to convert my project to Jest, when creating a new lib, I expect to, at least, not have a * Karma* configuration file on this lib.
Also, if possible, have the correct
jestSetupfiles.Describe alternatives you've considered
If it cannot be done automatically, create a script to, at least, remove the karma file.
The text was updated successfully, but these errors were encountered: