You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is meant as general tracker for things that should be implemented after #44 landed.
As such we have to decide if we want to keep on supporting IE or not. I personally would drop the support in another semver-major. Otherwise it's difficult to keep up with changes and implement new features.
If someone would still want to use the IE they would have to transpile the code with babel accordingly and hope everything works well. I guess most features that someone in the IE would use would keep on working and it's mainly the tests that are difficult to keep up (like new language features are not required in the IE so code branches working specially for new types would not be taken etc).
@BridgeAR are you maintaining this library these days? It could do with a new sync I think. throws, rejects and others seem to be outdated or missing (I've resorted to manual polyfills for both in different situations). Also yeah, error messages are pretty wonky when seen side-by-side with Node's.
Activity
[-]Implement assertion error messages[/-][+]Implement assertion error messages and more[/+]BridgeAR commentedon May 6, 2019
This issue is meant as general tracker for things that should be implemented after #44 landed.
As such we have to decide if we want to keep on supporting IE or not. I personally would drop the support in another semver-major. Otherwise it's difficult to keep up with changes and implement new features.
BridgeAR commentedon May 6, 2019
If someone would still want to use the IE they would have to transpile the code with babel accordingly and hope everything works well. I guess most features that someone in the IE would use would keep on working and it's mainly the tests that are difficult to keep up (like new language features are not required in the IE so code branches working specially for new types would not be taken etc).
rvagg commentedon Jan 10, 2020
@BridgeAR are you maintaining this library these days? It could do with a new sync I think.
throws,rejectsand others seem to be outdated or missing (I've resorted to manual polyfills for both in different situations). Also yeah, error messages are pretty wonky when seen side-by-side with Node's.