Skip to content
Browse files

src: add process.binding('config')

It turns out that userland likes to override process.config with
their own stuff. If we want to be able to depend on it in any way,
we need our own internal mechanism.

This adds a new private process.binding('config') that is
intended to serve as a container for internal flags and compile
time configs that need to be passed on to the JS layer.

PR-URL: #6266
Reviewed-By: Ben Noordhuis <>
  • Loading branch information...
jasnell committed Apr 19, 2016
1 parent 7f11634 commit 2e974cdd8ce1829d50b8e8713633e4510b2d3e76
Showing with 37 additions and 0 deletions.
  1. +1 −0 node.gyp
  2. +36 −0 src/
@@ -130,6 +130,7 @@
@@ -0,0 +1,36 @@
#include "node.h"
#include "env.h"
#include "env-inl.h"
#include "util.h"
#include "util-inl.h"

namespace node {

using v8::Context;
using v8::Local;
using v8::Object;
using v8::Value;
using v8::ReadOnly;

// The config binding is used to provide an internal view of compile or runtime
// config options that are required internally by lib/*.js code. This is an
// alternative to dropping additional properties onto the process object as
// has been the practice previously in

do { \
target->DefineOwnProperty(env->context(), \
OneByteString(env->isolate(), str), \
True(env->isolate()), ReadOnly).FromJust(); \
} while (0)

void InitConfig(Local<Object> target,
Local<Value> unused,
Local<Context> context) {
// Environment* env = Environment::GetCurrent(context);

This comment has been minimized.

Copy link

trevnorris Apr 26, 2016


Accidentally left dead code here? Actually, why wasn't this squashed with the other?

This comment has been minimized.

Copy link

jasnell Apr 26, 2016

Author Member

this commit is going to get backported to v5 and v4 where the other flags aren't relevant. The comment could have been removed but landing this separate was intentional to make backporting easier


} // namespace node


0 comments on commit 2e974cd

Please sign in to comment.
You can’t perform that action at this time.