Replacing console error with an onError option

[ekynoxe]

I had a first stab a #19.

This is ultra simplistic and very simple, but it does the initial job of delegating error handling the the user.

One thing I didn't really like was the check for process.env.NODE_ENV which might not be available, therefore you'd potentially throw errors in production code anyway.

I've only done the makeDecryptor method so far, but maybe we need to add this to the makeEncryptor method too?

[maxdeviant]

I would prefer this check to be typeof onError === 'function', as that would prevent it from trying to call some truthy non-function.

[ekynoxe]

Yes, you're right. I'll update this.
Do you think this should also be added to the makeEncryptor method as well?

[maxdeviant]

@ekynoxe Yea, the process.env.NODE_ENV check isn't the greatest, and delegating the error handling to the consumer makes it their choice how they want to handle it.

I think the other place where we should use onError is here instead of throwing an error.

[ekynoxe]

Regarding your comment on the sync.js file, is it strictly necessary? I believe this will be caught by the try/catch where I did my original update, won't it?