Code Coverage Report issue

[Jamee77]

I get the below issue while trying to run the command
ng test (applicaitonname) --watch=false --code-coverage

Issue:
See http://localhost/api-reference/runtime-options.html#options-to-control-prototype-access for details
Handlebars: Access has been denied to resolve the property "functions" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:

Please suggest what to do.

[ewolfe]

I just got the same error after updating a handful of dependencies (istanbul, istanbul-instrumenter-loader, and karma-coverage)

[Jamee77]

I just got the same error after updating a handful of dependencies (istanbul, istanbul-instrumenter-loader, and karma-coverage)

Were you able to fix it?

[ewolfe]

Well... kind of? I'm going down a rabbit hole of updating all my dependencies:

I think one of my initial root causes was a mismatch of dependencies. But I couldn't tell you exactly what the culprit was. So I just started slowly hacking away it in as small as chunks as I could do.

(PS, don't read too much into the failed builds in my screenshot. It's unrelated to the code coverage report issue).

[alan-agius4]

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.

If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

[jordivila]

I was facing the same issue. It might be related to handlebars-lang/handlebars.js#1636

Exception message:

Handlebars: Access has been denied to resolve the property "statements" because it is not an "own property" of its parent.

Test succeed but coverage report is not well formed. Only happens when --code-coverage is used.
Once I updated karma-coverage-istanbul-reporter to 2.1.1 the issue is fixed.

[angular-automatic-lock-bot]

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.}