Incompatibility with chai@4
See original GitHub issuechai version: 4.0.0 chai-spies version: 0.7.1 Node.js version: 7.10.0
expect(spy).to.be.called.with(...)
fails with:
Error: Invalid Chai property: _his. Did you mean "is"?
at Object.proxyGetter [as get] (node_modules/chai/lib/chai/utils/proxify.js:63:17)
at Proxy.assertWith (node_modules/chai-spies/lib/spy.js:283:29)
at Proxy.chainableMethodWrapper (node_modules/chai/lib/chai/utils/addChainableMethod.js:113:49)
Besides that, if this is a breaking change in the public API for plugin authors, it should probably have been mentioned in the release notes for chai@4.0.0
.
Thanks!
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (4 by maintainers)
Top Results From Across the Web
(PDF) Incompatibility between Students' Body Measurements ...
The aim of this study was to examine possible incompatibility between students' body measures and school chairs they use.
Read more >[PDF] Incompatibility between Students' Body Measurements ...
The results revealed a high level of incompatibility between the chair dimensions and the anthropometric characteristics of the primary boy school students ...
Read more >CHAIR COMPATIBILITY MATRIX - DentalEZ
We are continually evaluating the fit of our Hands Free HVE Holder on multiple patient chairs, and will continue to add more models...
Read more >Chair Gensler: Crypto Markets Not Incompatible ... - SEC.gov
Yet the core principles have remained the same. "Nothing about the crypto markets is incompatible with the securities laws," Chair Gensler said.
Read more >Copyright in chairs not restored despite incompatibility with ...
MONTIS DESIGN BV V GOOSSENS MEUBELEN BV CASE C-169/15. This case involves a CJEU preliminary ruling on the effect of national laws, which...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So according to the linked issue, only the master branch of this plugin is working. The tagged npm release 0.7.1 is not. Can we get a release to bump or are we all forced to tag this package to master?
"chai-spies": "git://github.com/chaijs/chai-spies.git#master"
or if you like to lock it to current HEAD:
"chai-spies": "git://github.com/chaijs/chai-spies.git#b11aeebf"
can we get a quick bump to 0.7.2 with current master? locking package at certain commit/branch breaks our deploy 😞