implementation
entry pointObject.keys
is not presentnode
v11.8
, v10.15
, v8.15
, v6.16
npm audit
from nsp
window.applicationCache
, to avoid issues with latest Chrome on HTTP (#46)pageYOffset
) on window
to avoid reflow (#32)height
and width
keys on window
to avoid reflow (#31)window.external
makes Object.keys
thrownode
v6.2
, v5.10
, v4.4
tape
, jscs
, nsp
, eslint
, @ljharb/eslint-config
jscs
, eslint
, @ljharb/eslint-config
io.js
v3.3
, node
v4.2
eslint
, tape
, @ljharb/eslint-config
, jscs
176f03335e
/ https://github.com/es-shims/es5-shim/issues/275 that doesn't break dontEnum/constructor fixes in IE 8.io.js
v2.4
indexOf
(#14)Array.isArray
no-shadow
rule, as well as an IE 8 bug caused by engine NFE shadowing bugs.localStorage.constructor.prototype === localStorage
throwsio.js
v2.3
nsp
, eslint
Object.keys
not working with arguments
node
and io.js
jscs
, tape
, eslint
, nsp
, is
, editorconfig-tools
, covert
object-keys
more robust against later environment tampering" to maintain ES3 complianceobject-keys
more robust against later environment tampering