Changelog History
Page 3
-
v4.0.0 Changes
May 11, 2020- ⚡️ Updated dependencies, base files, and editions using boundation
- Minimum required node version changed from
node: >=8
tonode: >=10
to keep up with mandatory ecosystem changes
-
v3.3.0 Changes
December 09, 2019- ⚡️ Updated dependencies, base files, and editions using boundation
-
v3.2.0 Changes
December 01, 2019- ⚡️ Updated dependencies, base files, and editions using boundation
-
v3.1.0 Changes
December 01, 2019- ⚡️ Updated dependencies, base files, and editions using boundation
-
v3.0.0 Changes
November 18, 2019- ⚡️ Updated dependencies, base files, and editions using boundation
- Minimum required node version changed from
node: >=0.12
tonode: >=8
to keep up with mandatory ecosystem changes
-
v2.6.0 Changes
November 13, 2019- ⚡️ Updated dependencies, base files, and editions using boundation
-
v2.5.1 Changes
January 21, 2019📚 Fixed a readme documentation inconsistency
🛠 Fixed node v0.12 and v4 support (regression since v2.5.0)
-
v2.5.0 Changes
January 21, 2019As the detection algorithms are result returns, with the asynchronous signatures just wrappers, we have changed
isText
,isBinary
, andgetEncoding
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 ofisTextSync
(a method which only lingers for backwards compatibility) -
isBinary
, which you should use instead ofisBinarySync
(a method which only lingers for backwards compatibility) -
getEncoding
, which you should use instead ofgetEncoding
(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 ofisText
's callback signature (a signature which only lingers for backwards compatibility) -
isBinaryCallback
, which you should use instead ofisBinary
's callback signature (a signature which only lingers for backwards compatibility) -
getEncodingCallback
, which you should use instead ofgetEncoding
'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 wrapsisText
with a promise signature -
isBinaryPromise
which wrapsisBinary
with a promise signature -
getEncodingPromise
which wrapsgetEncoding
with a promise signature
-
isBinary
method now correctly returnsnull
instead oftrue
when no inputs are provided✅ Added tests for all methods
-
v2.4.2 Changes
January 21, 2019- 📦 Added more keywords to
package.json
- 📦 Added more keywords to
-
v2.4.1 Changes
January 21, 2019- 📦 README now elaborates on the operation of this package