Package Exports

to-type

This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (to-type) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.

Readme

to-type

The way typeOf should be

Linux & OSX	Windows

This is a node implementation of angus-c's Fixing the JavaScript typeof operator.

Install

npm install --save to-type

Usage

const toType = require('to-type');

toType([1, 2, 3]);
//=> 'array'

toType(/a-z/);
//=> 'regexp'

toType(new Number(4));
//=> 'number'

toType(new String('abc'));
//=> 'string'

About

JavaScript's typeOf function sucks. It has returned vague values since 1997 and always will be due to backwards compatibility. It seems like nearly every call returns object. Don't believe me?

typeof {a: 4};
//=> 'object'

typeof [1, 2, 3];
//=> 'object'

typeof new ReferenceError;
//=> 'object'

typeof new Date;
//=> 'object'

typeof /a-z/;
//=> 'object'

typeof JSON;
//=> 'object'

typeof new Number(4);
//=> 'object'

typeof new String('abc');
//=> 'object'

Did I hear you say that was not enough proof?

typeof new Boolean(true);
//=> 'object'

Wait, you're still not convinced?

typeof Math;
//=> 'object'

to-type fixes these vague outputs by returning the types you expect to see.

API

toType(target)

target

Type: string

returns

Type: string
Description: The return value is always lowercased.

More Examples

toType({a: 4});
//=> 'object'

toType(new Date());
//=> 'date'

toType(Math);
//=>'math'

toType(JSON);
//=> 'json'

toType(new Number(4));
//=> 'number'

toType(new String('abc'));
//=> 'string'

toType(new Boolean(true));
//=> 'boolean'

toType(new ReferenceError());
//=> 'error'


//es2015 and newer
toType(Promise);
//=> 'function'

toType(Symbol());
//=> 'symbol'

License

If you like this, star it. If you want to follow me, follow me.