question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Deprecation warning with Jasmine-Core@3.3.0

See original GitHub issue

Jasmine-Core 3.3.0 release nodes

Introduce a configuration object to Env deprecating old single use functions

The test fails as well, however I am not sure if that is something that could be fixed here.

HeadlessChrome 0.0.0 (Mac OS X 10.13.6) ERROR: 'DEPRECATION:', 'Setting specFilter directly on Env is deprecated, please use the specFilter option in `configure`'
HeadlessChrome 0.0.0 (Mac OS X 10.13.6) ERROR
  {
    "message": "TypeError: this.deprecated is not a function\n    at Env.throwOnExpectationFailure (/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:1079:12)\n    at setOption (/node_modules/karma-jasmine/lib/adapter.js:354:7)\n    at ContextKarma.start (/node_modules/karma-jasmine/lib/adapter.js:343:5)\n    at ContextKarma.loaded (http://localhost:9876/context.js:168:14)\n    at http://localhost:9876/context.html:47:22",
    "str": "TypeError: this.deprecated is not a function\n    at Env.throwOnExpectationFailure (/node_modules/jasmine-core/lib/jasmine-core/jasmine.js:1079:12)\n    at setOption (/node_modules/karma-jasmine/lib/adapter.js:354:7)\n    at ContextKarma.start (/node_modules/karma-jasmine/lib/adapter.js:343:5)\n    at ContextKarma.loaded (http://localhost:9876/context.js:168:14)\n    at http://localhost:9876/context.html:47:22"
  }
HeadlessChrome 0.0.0 (Mac OS X 10.13.6): Executed 0 of 0 ERROR (0.122 secs / 0 secs)

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:23
  • Comments:19 (10 by maintainers)

github_iconTop GitHub Comments

10reactions
yasiryccommented, Jan 2, 2019

Any update when the fix would be published? npm still shows 3.3.0 as latest version

7reactions
MauricioPenteadocommented, Feb 13, 2019

I fixed it on my side using the follow upgrades:

“jasmine-core”: “^3.3.0”, “karma-jasmine”: “^2.0.1”, “karma-jasmine-html-reporter”: “^1.4.0”,

Read more comments on GitHub >

github_iconTop Results From Across the Web

jasmine-npm triggers deprecation warnings in jasmine-core
It looks like jasmine-npm uses a couple of deprecated Env methods. If I install it in an empty directory, run jasmine init ,...
Read more >
How to fix with statement deprecation warning - Stack Overflow
Basically, this stops any DeprecationWarning from displaying. Here's a couple links for understanding warnings. Hope this helped!
Read more >
The Complete Guide for Deprecation Warnings in Rails
In Rails, all deprecation warnings start with DEPRECATION WARNING: , so you can search for that string in your logs. When it comes...
Read more >
How we automatically fixed thousands of Ruby 2.7 ... - GitLab
The upgrade to Ruby 2.7 for GitLab involved thousands of deprecation warnings across hundreds of files. Here's how we fixed most of them....
Read more >
Upgrading to jasmine 4.0
Jasmine 3.99 issues deprecation warnings for most code that uses APIs that are removed or changed in incompatible ways in 4.0. We recommend...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found