SortedMap.some is broken in v2.0.0 about collections HOT 11 CLOSED

Can you let me know how you ended up with 2.0.0? Did it come down with a plain npm install?

from collections.

Yes. I just did a plain npm install.

Latest version on npm is 2.0.0

Cheers
On Mar 20, 2014 7:55 PM, "Kris Kowal" [email protected] wrote:

Can you let me know how you ended up with 2.0.0? Did it come down with a
plain npm install?

Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-38231036
.

from collections.

Thank you for the test. I have reproduced the problem on the v2 branch. It is a regression, not seen on the v1 branch.

Oh, npm. I’ll have to unpublish.

from collections.

Thanks. I’ve updated the latest tag in npm. If you reinstall, you should get the correct version now.

from collections.

No problems

Thanks for your work :)
On Mar 20, 2014 8:06 PM, "Kris Kowal" [email protected] wrote:

Thanks. I've updated the latest tag in npm. If you reinstall, you should
get the correct version now.

Reply to this email directly or view it on GitHubhttps://github.com//issues/62#issuecomment-38231903
.

from collections.

I updated to v2.0.1.

Still getting the same error...

from collections.

You need to downgrade to 1.0.2.

from collections.

You mean before installing, downgrade to 1.0.2 (or remove the package)?

from collections.

npm rm collections --save
npm install collections --save

If that does not give you 1.0.2, something is broken.

from collections.

Oh, ok. I just thought that 2.0.1 fixed the issue.

Will keep using v1.0.2.

Cheers

from collections.

Fixed in v2 branch.

from collections.