Investigate potential remaining items for Chai v4 support about chai-immutable HOT 8 CLOSED

@astorije no problem, I'll give it a try tomorrow when I have chance to test it :)

from chai-immutable.

@astorije yep I'd agree, I believe it's due to the way the object is created for comparison and something has changed in Chai.

from chai-immutable.

Is there any update on version 2?

from chai-immutable.

Hi @probedb! I stiiiill haven't finished this, I'm sorry. I'm almost there, there are a couple things left I want to look at before publishing this. Sorry about this!

In the meantime, I have just published v2.0.0-alpha.2 with the latest master. It is compatible with Chai v4 and requires Node v6+. Could you try it (npm install --save-dev chai-immutable@next or yarn add --dev chai-immutable@next) and let me know if you notice anything wrong with it?

Thanks!

from chai-immutable.

@probedb, any luck?

from chai-immutable.

Hey @probedb, I have just released v2.0.0-rc.2 which hopefully is the last step before full Chai v4 support (finally!). Mind giving it a shot and letting me know if it works as expected for you?

from chai-immutable.

Sorry @astorije ended up busy! I've updated to 2.0.0-rc.2 and chai 4.1.2 and the only issues I have are: when doing:

expect(callback.args[0][0]).to.eql(new Error('something went wrong'))

I get:

AssertionError: expected [Error: something went wrong] to deeply equal [Error: something went wrong]
      + expected - actual

But I've had this before with error objects, there's 13 errors like this after the update.

from chai-immutable.

I suspect this is unrelated to chai-immutable (or immutable itself), therefore not with the v2 either. Do you concur?

from chai-immutable.