Closed marleypowell closed 2 years ago
We have seen some problems with upgraded nx / angular workspaces in the past where something in the migration hasn't generated correct configuration.
From your diagnostics report, we can't see anything that may be causing the problem.
Can you please confirm that your Angular tests are working from the command-line?
We set up an Angular v12 application and migrated it to v14 with karma tests and it is working for us. If your tests are working from the command-line and not Wallaby, as a next step, could you please create a new v14 workspaces with Angular and configure it to use Karma as the test runner.
After you have created the new v14 workspace, please confirm that Wallaby is working for you (you shouldn't have any issues).
Once you've done that, you should then be able to analyze the differences between your upgraded project configuration and the new project configuration to determine why it's not working and apply the differences to your upgraded project.
We have seen some problems with upgraded nx / angular workspaces in the past where something in the migration hasn't generated correct configuration.
From your diagnostics report, we can't see anything that may be causing the problem.
Can you please confirm that your Angular tests are working from the command-line?
We set up an Angular v12 application and migrated it to v14 with karma tests and it is working for us. If your tests are working from the command-line and not Wallaby, as a next step, could you please create a new v14 workspaces with Angular and configure it to use Karma as the test runner.
After you have created the new v14 workspace, please confirm that Wallaby is working for you (you shouldn't have any issues).
Once you've done that, you should then be able to analyze the differences between your upgraded project configuration and the new project configuration to determine why it's not working and apply the differences to your upgraded project.
This is still a problem.
I have created a reproduction here: https://github.com/marleypowell/nx-angular-wallabyjs-bug
Commands used:
npx create-nx-workspace --name wallabyjs-repro2 --preset=apps
yarn nx generate @nrwl/angular:application app1 --style=scss --unitTestRunner=karma
Thanks for the repo and instructions for reproducing. I tried this again on MacOS and it was fine but then tried and Windows and it's failing.
Will let you know when we have a fix for you.
We've identified some breaking changes in the latest version of NX for Windows. It seems to be caused by code within Angular, because of an incompatibiltity between NX and Angular workspace format / resolution.
Could you please update to Wallaby v1.0.1313
. It should work for you.
Great it's working now. Thanks for the quick fix 🙂
Issue description or question
After upgrading to angular v14 we have started seeing these errors which stop wallaby from working:
Failed to load configuration file: Automatic Angular CLI configuration error: Could not find a local workspace. Are you in a project?
Wallaby diagnostics report