istextorbinary - npm Package Versions

v2.6.0 2019 November 13

• Updated dependencies, base files, and editions using boundation

v2.5.1 2019 January 21

• Fixed a readme documentation inconsistency

• Fixed node v0.12 and v4 support (regression since v2.5.0)

v2.5.0 2019 January 21

As the detection algorithms are result returns, with the asynchronous signatures just wrappers, we have changed isText, isBinary, and getEncoding to return the result if no callback was provided to them, maintaining backwards compatibility, but encouraging intuitive usage of the methods with the least overhead.

• The following methods have had return signatures added to them, which should be the preferable usage:

  • isText, which you should use instead of isTextSync (a method which only lingers for backwards compatibility)
  • isBinary, which you should use instead of isBinarySync (a method which only lingers for backwards compatibility)
  • getEncoding, which you should use instead of getEncoding (a method which only lingers for backwards compatibility)

• If you require callback usage, the following callback wrapper methods have been added:

  • isTextCallback, which you should use instead of isText's callback signature (a signature which only lingers for backwards compatibility)
  • isBinaryCallback, which you should use instead of isBinary's callback signature (a signature which only lingers for backwards compatibility)
  • getEncodingCallback, which you should use instead of getEncoding's callback signature (a signature which only lingers for backwards compatibility)

• If you require promise usage, the following promise wrapper methods have been added:

  • isTextPromise which wraps isText with a promise signature
  • isBinaryPromise which wraps isBinary with a promise signature
  • getEncodingPromise which wraps getEncoding with a promise signature

• isBinary method now correctly returns null instead of true when no inputs are provided

• Added tests for all methods

v2.4.2 2019 January 21

• Added more keywords to package.json

v2.4.1 2019 January 21

• README now elaborates on the operation of this package

v2.4.0 2019 January 20

• Asynchronous methods now try...catch the synchronous methods to ensure an error from invalid inputs would be given to the callback.
  • Before they would not do any try...catch so if invalid inputs were given, the error would throw.
• The JSDoc documentation has been updated for accuracy.
  • It previously indicated that the return types of the sync methods could have been an error instance, this was incorrect, they would throw if received invalid inputs.
  • It previously indicated that the result for of the async getEncoding callback was a boolean, this was incorrect, it would be the string result of getEncodingSync.
• Updated base files and editions using boundation

v2.3.0 2018 November 7

• Ensure that textextensions and binaryextensions are the latest versions at the time of publishing
• Updated base files and editions using boundation