Messy error returns: Sometimes a string, sometimes an Error object

[lll000111]

Looking at all reject() calls in https://github.com/wkh237/react-native-fetch-blob/blob/master/fs.js

Some have a string as argument, many others first do a new Error() around the string message (better - stacktrace is created).

Sometimes there is contradiction for the same error message:

• Line 159

return Promise.reject(new Error('Invalid argument "path" '))

• Line 172

return Promise.reject('Invalid argument "path" ')

RNFetchBlobWriteStream again uses strings for the reject-value in both its methods (write, close).

I would like to propose to use new Error(message) - always.