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
One of the major API differences currently between node_io and dart:io is the errors: where dart:io throws various subclasses of IOException, node_io just throws Node.js's raw exceptions. This makes it difficult to use node_io to write error-safe code that works with both Dart and Node. It would be great if these exceptions were caught and wrapped in Dart-style exception classes to increase compatibility.
The text was updated successfully, but these errors were encountered:
One of the major API differences currently between
node_io
anddart:io
is the errors: wheredart:io
throws various subclasses ofIOException
,node_io
just throws Node.js's raw exceptions. This makes it difficult to usenode_io
to write error-safe code that works with both Dart and Node. It would be great if these exceptions were caught and wrapped in Dart-style exception classes to increase compatibility.The text was updated successfully, but these errors were encountered: