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
@nrwl/angular:karma-project does not get config properly #9234
Comments
Hi @MasterSaberD1996
can you explain further how you get your workspace into that state? creating a project with karma as the test runner will create the root config. So if you can clarify what you you mean by "running the tests is impossible" so I can figure out how to fix this. in the mean time I'll update the karma project generator to create the root karma config if it's not present. Thanks! |
…arma-project generator when using the karma-project generator directory ensure the karma generator (install deps/root config) is called if the root karma config isn't present ISSUES CLOSED: #9234
…arma-project generator when using the karma-project generator directory ensure the karma generator (install deps/root config) is called if the root karma config isn't present ISSUES CLOSED: #9234
…arma-project generator when using the karma-project generator directory ensure the karma generator (install deps/root config) is called if the root karma config isn't present ISSUES CLOSED: #9234
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Currently the command creates only one karma.conf.js in the default application folder even if no other configs exist. As well, when you do get a base config created it does not pass the config to any calling config files.
Expected Behavior
Expected behavior is that running
nx g @nrwl/angular:karma-project
should create a base config if no config exists and the base config should "return" itself to pass itself to any child configs that may exist;Steps to Reproduce
The output of the command with no preexisting config shows:
Inside that karma.conf.js:
running the same command with a config file already existing also creates a situation where running the tests is impossible:
BASE KARMA CONFIG
CHILD KARMA CONFIG
Environment
Node : 16.13.2
OS : win32 x64
npm : 8.3.0
nx : 13.8.5
@nrwl/angular : 13.8.5
@nrwl/cli : 13.8.5
@nrwl/cypress : 13.8.5
@nrwl/detox : undefined
@nrwl/devkit : 13.8.5
@nrwl/eslint-plugin-nx : 13.8.5
@nrwl/express : undefined
@nrwl/jest : 13.8.5
@nrwl/js : undefined
@nrwl/linter : 13.8.5
@nrwl/nest : undefined
@nrwl/next : undefined
@nrwl/node : undefined
@nrwl/nx-cloud : 13.1.6
@nrwl/react : undefined
@nrwl/react-native : undefined
@nrwl/schematics : undefined
@nrwl/storybook : 13.8.5
@nrwl/tao : 13.8.5
@nrwl/web : undefined
@nrwl/workspace : 13.8.5
typescript : 4.5.5
rxjs : 7.4.0
Community plugins:
@angular/animations: 13.2.5
@angular/common: 13.2.5
@angular/compiler: 13.2.5
@angular/core: 13.2.5
@angular/forms: 13.2.5
@angular/platform-browser: 13.2.5
@angular/platform-browser-dynamic: 13.2.5
@angular/router: 13.2.5
@angular-devkit/build-angular: 13.2.5
@angular/cli: 13.2.5
@angular/compiler-cli: 13.2.5
@angular/language-service: 13.2.5
The text was updated successfully, but these errors were encountered: