In JS, `object` is treated as 'any'

TypeScript Version: 3.0.0-dev.20180711

Code

/** @typedef {object} T */
/** @type {T} */
const x = 0;

Expected behavior:

Error at x: 0 is not an object.

Actual behavior:

No error.

[ExE-Boss]

@sandersn I’ve personally been using:

/** @typedef {(typeof Object.create) extends (arg0: infer T, ...args: any) => any
	? (T extends null | undefined ? never : T) : never} obj */

Which is the inlined form of:

/** @typedef {NonNullable<Parameters<typeof Object.create>[0]>} obj */

[sandersn]

@ExE-Boss you can use the type NonPrimitive = object in one of your own d.ts files. Unfortunately, lots of existing JS code uses object to mean any or unknown, even projects like webpack that compile regularly with typescript.