Lots of handlebars warnings with text+coverage reporter

[sobolevn]

🐛 Bug Report

I get this when I am running jest:

> cross-env NODE_ENV=test jest


[vue-jest]: no .babelrc found, skipping babel compilation


[vue-jest]: no .babelrc found, skipping babel compilation

 PASS  tests/pages/index.spec.ts (5.069s)
  unit tests for Index view
    ✓ should have three comments (36ms)
    ✓ should load new comments on actions (41ms)
  snapshot test for Index view
    ✓ should match the snapshot (72ms)

 PASS  tests/components/action-bar.spec.ts (5.061s)
  unit tests for ActionBar component
    ✓ should have one button (42ms)
    ✓ should call fetchComments action (7ms)
    ✓ should match the snapshot (33ms)

 PASS  tests/components/comment.spec.ts
  unit tests for Comment component
    ✓ should have valid props (28ms)
    ✓ should have two buttons (13ms)
    ✓ should have correct values (12ms)
    ✓ should change rating: {"delta": 1, "styleName": "comment-positive"} (10ms)
    ✓ should change rating: {"delta": -1, "styleName": "comment-negative"} (4ms)
  snapshot tests for Comment component
    ✓ should match the snapshot (17ms)

-------------------------|----------|----------|----------|----------|----------------
---|
File                     |  % Stmts | % Branch |  % Funcs |  % Lines | Uncovered Line 
#s |
-------------------------|----------|----------|----------|----------|----------------
---|
All files                |    95.97 |    82.35 |       90 |    96.94 |                   |
 components              |    95.45 |      100 |       80 |       95 |                   |
  ActionBar.vue          |      100 |      100 |      100 |      100 |                   |
  AppLogo.vue            |      100 |      100 |      100 |      100 |                   |
  Comment.vue            |    91.67 |      100 |       50 |    90.91 |                60 |
 logic                   |      100 |      100 |      100 |      100 |                   |
  store.ts               |      100 |      100 |      100 |      100 |                   |
  tokens.ts              |      100 |      100 |      100 |      100 |                   |
 logic/comments          |    95.12 |    77.78 |      100 |      100 |                   |
  models.ts              |      100 |      100 |      100 |      100 |                   |
  module.ts              |    94.87 |    77.78 |      100 |      100 |             50,56 |
 logic/comments/services |      100 |      100 |      100 |      100 |                   |
  api.ts                 |      100 |      100 |      100 |      100 |                   |
 mixins                  |      100 |      100 |      100 |      100 |                   |
  typed-store.ts         |      100 |      100 |      100 |      100 |                   |
 pages                   |    83.33 |      100 |       50 |    81.82 |                   |
  index.vue              |    83.33 |      100 |       50 |    81.82 |             56,57 |
 plugins                 |      100 |      100 |      100 |      100 |                   |
  type-di.ts             |      100 |      100 |      100 |      100 |                   |
 store                   |      100 |       50 |      100 |      100 |                   |
  index.ts               |      100 |       50 |      100 |      100 |                30 |
-------------------------|----------|----------|----------|----------|-------------------|
Handlebars: Access has been denied to resolve the property "statements" because it is not an "own property" of its parent.
You can add a runtime option to disable the check or this warning:
See http://localhost:8080/api-reference/runtime-options.html#options-to-control-prototype-access for details
...

Problem part:

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

It is actually VERY long. It has like hundreds of lines.
Full log is here: https://travis-ci.com/wemake-services/wemake-vue-template/builds/143977902#L759

To Reproduce

Steps to reproduce the behavior:

1. Create new app: https://github.com/wemake-services/wemake-vue-template
2. Install deps with npm i
3. Run npm test

Expected behavior

I expect the tests to pass without any warnings.

envinfo

» npx envinfo --preset jest
npx: installed 1 in 1.988s

  System:
    OS: macOS Mojave 10.14.5
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
  Binaries:
    Node: 12.14.0 - ~/.nvm/versions/node/v12.14.0/bin/node
    Yarn: 1.9.4 - /usr/local/bin/yarn
    npm: 6.13.4 - ~/.nvm/versions/node/v12.14.0/bin/npm
  npmPackages:
    jest: ^24.9.0 => 24.9.0 

[djErock]

This is about the most annoying thing of all time... I posted an issue on handlebars github as I tracked down this -->

function checkWhiteList(protoAccessControlForType, propertyName) {
	  if (protoAccessControlForType.whitelist[propertyName] !== undefined) {
	    return protoAccessControlForType.whitelist[propertyName] === true;
	  }
	  if (protoAccessControlForType.defaultValue !== undefined) {
	    return protoAccessControlForType.defaultValue;
	  }
	  // eslint-disable-next-line no-console
	  logger.log('error', 'Handlebars: Access has been denied to resolve the property "' + propertyName + '" because it is not an "own property" of its parent.\n' + 'You can add a runtime option to disable the check or this warning:\n' + 'See http://localhost:8080/api-reference/runtime-options.html#options-to-control-prototype-access for details');
	  return false;
	}

They disabled a lint rule and it got into the release... SMDH

Issue in Jest is with this dependency -->

"istanbul-reports": {
      "version": "2.2.6",
      "resolved": "https://artifactoryprod.es.ad.adp.com/artifactory/api/npm/caet-npm/istanbul-reports/-/istanbul-reports-2.2.6.tgz",
      "integrity": "sha1-e08mYNgrKTA6j+YJH4ykvwWNoa8=",
      "dev": true,
      "requires": {
        "handlebars": "^4.1.2"
      }
    },

Had to install

npm i -D handlebars@4.5.0

as a dev dependency and the console logs went away... Pretty klugey answer but will do until one of the two sides figures it out... or someone submits a PR to handlebars... *** slowly whistles and walks away

[shellyhu3]

I'm having the same issue and just tried installing handlebars as a dev dependency but I'm still getting the warnings.

[djErock]

I'm having the same issue and just tried installing handlebars as a dev dependency but I'm still getting the warnings.

rm -rf node_modules && rm -rf package-lock.json && npm i && npm test

Remove the caret in front of 4.5.0 in package.json as well

[silver-xu]

Just tried the above solution, still displaying all the warnings

I'm having the same issue and just tried installing handlebars as a dev dependency but I'm still getting the warnings.

rm -rf node_modules && rm -rf package-lock.json && npm i && npm test

Remove the caret in front of 4.5.0 in package.json as well

[djErock]

Just tried the above solution, still displaying all the warnings

I'm having the same issue and just tried installing handlebars as a dev dependency but I'm still getting the warnings.

rm -rf node_modules && rm -rf package-lock.json && npm i && npm test
Remove the caret in front of 4.5.0 in package.json as well

Can you do a find in your package-lock/yarn-lock for which handlebars version is installed?

[Nonary]

I have the exact same problem, except I don't even get coverage reports. It just spams hundreds of lines, and the final report makes the html file with the correct color coding (for percentages, like green red, etc) but the numbers are not there.

Also tried the suggestions above, made no difference. My yarn.lock has handlebars as a dev dependency at 4.70

[djErock]

I have the exact same problem, except I don't even get coverage reports. It just spams hundreds of lines, and the final report makes the html file with the correct color coding (for percentages, like green red, etc) but the numbers are not there.

Also tried the suggestions above, made no difference. My yarn.lock has handlebars as a dev dependency at 4.70

I had the same issue... Downgrading Handlebars did the trick and now all my report is populated with data again and not just color codes.

[Nonary]

I have the exact same problem, except I don't even get coverage reports. It just spams hundreds of lines, and the final report makes the html file with the correct color coding (for percentages, like green red, etc) but the numbers are not there.
Also tried the suggestions above, made no difference. My yarn.lock has handlebars as a dev dependency at 4.70

I had the same issue... Downgrading Handlebars did the trick and now all my report is populated with data again and not just color codes.

I can't seem to downgrade it, I put in my package.json to install a specific version and it will install that version as well as the 4.7.0 version.

[djErock]

I have the exact same problem, except I don't even get coverage reports. It just spams hundreds of lines, and the final report makes the html file with the correct color coding (for percentages, like green red, etc) but the numbers are not there.
Also tried the suggestions above, made no difference. My yarn.lock has handlebars as a dev dependency at 4.70

I had the same issue... Downgrading Handlebars did the trick and now all my report is populated with data again and not just color codes.

I can't seem to downgrade it, I put in my package.json to install a specific version and it will install that version as well as the 4.7.0 version.

rm -rf node_modules && rm -rf package-lock.json && npm i && npm test

Remove the caret in front of 4.5.0 in package.json as well

[sobolevn]

Thanks for your help! However, 4.5.0 is reported as unsafe.

+ handlebars@4.5.0
updated 1 package and audited 899407 packages in 22.265s

54 packages are looking for funding
  run `npm fund` for details

found 6 high severity vulnerabilities
  run `npm audit fix` to fix them, or `npm audit` for details

[nknapp]

See handlebars-lang/handlebars.js#1636. I think the problem is known and in work.