-
-
Notifications
You must be signed in to change notification settings - Fork 33.4k
Closed
Labels
v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.
Description
- Version: 7.0
- Platform: Darwin local 14.5.0 Darwin Kernel Version 14.5.0: Thu Apr 21 20:40:54 PDT 2016; root:xnu-2782.50.3~1/RELEASE_X86_64 x86_64
In Node.js version <= 6.x.x
,
var nativeClass = Object.prototype.toString.call( global );
// returns '[object global]'
In Node.js version 7.0
,
var nativeClass = Object.prototype.toString.call( global );
// returns '[object Object]'
Based on the changelog, this is not listed as a notable and/or breaking change. Why did the internal class change and is this a permanent/intentional change?
Background: one reason why this is a notable change is that environment sniffers (i.e., packages which try and detect if the runtime is Node versus, say, a browser) commonly use the internal class of global
as means to identify a Node environment.
Metadata
Metadata
Assignees
Labels
v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.