Throw Error objects instead of strings

The problem

I noticed that there are several places where you throw a string. It’s considered best practice to only throw Error objects. When listening to an ondata event, it’s really unexpected to have a variable called err that is a string instead of an Error object.

[101arrowz]

I’ve managed to implement errors with codes in a very lightweight fashion; it’s even smaller than before. I will publish this in v0.7.0, hopefully in a few days.

[101arrowz]

In TypeScript, there is an enum type that compiles to pure numbers. So it could be done like in lower level languages:

enum InflateError {
  InvalidDistance,
  InvalidLength,
  UnexpectedEOF
}

try {
  inflateSync(something);
} catch (e) {
  if (e == InflateError.InvalidDistance) {
    // handle
  }
}

On reconsideration maybe it’s best just to use the system you suggested. I’ll look into implementing this for v0.7.0.