-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for libraries? #22
Comments
I just followed these instructions for adding testing Typescript with Jest: https://basarat.gitbooks.io/typescript/docs/testing/jest.html And now the project compiles fine. So I guess it's just a matter of having the schematic install the dependencies and adding the |
This blog describes how I got it working: https://medium.com/@ole.ersoy/unit-testing-your-angular-library-project-with-jest-42429a8716eb |
Thanks for looking into this. Library support is something I'd like to add at some point. I'll keep this issue open as a reminder. |
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
Please see if |
Is your feature request related to a problem? Please describe.
Running the schematic on an Angular application project seems to be working fine, but when I run it on a library project it fails.
Here are some sample errors that I'm seeing:
It looks like jest does not understand typescript in this case. I'm assuming that we just have to add the normal Jest / Typescript setup.
Describe the solution you'd like
Automatic addition of support for libraries when we run:
The text was updated successfully, but these errors were encountered: