Angular-cli: Cannot debug unit test with karma in CLI version 6.1.2

Created on 7 Aug 2018  路  5Comments  路  Source: angular/angular-cli

Versions

  • angular CLI: 6.1.2
  • angular-devkit/build-angular: ~0.7.2
  • ide: Webstorm 2018.2

Repro steps

The log given by the failure

  • Before angular-devkit/build-angular: 0.7.2(like 0.6.8), there is a problem with 'importing node_modules using Less'.
  • In angular-devkit/build-angular:0.7.2, unit test with karma can not debug(breakpoints cannot get into debug dialog) in Webstorm 2018.2, but the bug with importing node_modules fixed.

Desired functionality

  • Unit-test can run properly.

Mini repo for issue

  • angular-devkit/build-angular: 0.6.8 version with module import problem the link
  • angular-devkit/build-angular: 0.7.2 version with debug problem link

    Mention any other details that might be useful

devkibuild-angular medium regression bufix

Most helpful comment

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

All 5 comments

This seems like a bug but we'll need to look at a reproduction to find and fix the problem. Can you setup a minimal repro please?

You can read here why this is needed. A good way to make a minimal repro is to create a new app via ng new repro-app and adding the minimum possible code to show the problem. Then you can push this repository to github and link it here.

Sorry for forgetting to follow the issue rules.
I set up two mini repo for these two problems.
For the first one(Before angular-devkit/build-angular: 0.7.2(like 0.6.8)), the repo link,
For the second one(In angular-devkit/build-angular:0.7.2), the repo link
After consideration, I think the debug problem may caused by Webstorm adpting new devkit.
Thanks for helping.

@sawyerbutton are you still experiencing the issue?

I'm going to close this as fixed in the latest version. If you still experience this issue please create a new issue and follow the template.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_This action has been performed automatically by a bot._

Was this page helpful?
0 / 5 - 0 ratings