Skip to content

Instantly share code, notes, and snippets.

Created November 28, 2012 02:08
Show Gist options
  • Save paulirish/4158604 to your computer and use it in GitHub Desktop.
Save paulirish/4158604 to your computer and use it in GitHub Desktop.
Learn JavaScript concepts with recent DevTools features

Learn JavaScript concepts with the Chrome DevTools

Authored by Peter Rybin , Chrome DevTools team

In this short guide we'll review some new Chrome DevTools features for "function scope" and "internal properties" by exploring some base JavaScript language concepts.


Let's start with closures – one of the most famous things in JS. A closure is a function, that uses variables from outside. See an example:

function A(a, b, c) {
  var ar = [a, b, c];
  return function B(i) {
    return ar[i];

var b = A('Here', 'I', 'am');
console.log( b(1) );

The first statement calls A that creates local array, returns function B (saved in variable b) and finishes.

The second statement calls function B (b) that returns an array item. That means that array ar from A has remained existing since A finished. But where was it stored? Of course, in b! But how exactly? In some property maybe? No. It's a core language feature, that a function can bear outside variables and there is no other way to access them but calling the function.

From now on, the debugger makes it explicitly visible. Get a function instance b from the example above and expand its properties. A sub-node called <function scope> should be there. It's where values of all bound variables will be shown. Those are the variables the function will use when called.

Internal properties

The other thing that DevTools debugger now shows is internal properties.

Suppose your code got a value s and does the following operation:

s.substring(1, 4)  // returns 'ell'

Do you think that s is a string? Not necessarily. It also can be a string object wrapper. Try the following in watch expressions:


First is a regular string value, the second is a full-featured object. As confusing as it could be, the two values behave almost identically. But the second one has real properties and you can set your own too. Expand the properties list and you will notice, how it's not a completely regular object: it will have an internal property [[PrimitiveValue]] , where the original string value is stored. You cannot access this property from your code, but you can see it in DevTools debugger now.

Who else has internal properties? It's bound functions. This is also a sort of wrapping, but for functions. Try executing these 2 statements:

function Sum(a, b) { return a + b; }
var inc = Sum.bind(null, 1); // binds a=1

If you put Sum and inc in watch expression section and compare them, you'll learn, that both are functions. But inc is a non-transparent one: you cannot see neither its text nor open its declaration, much unlike Sum.

That's how bound functions work. However, since now all the necessary data is shown in debugger as internal properties: among other properties of 'inc' (not very interesting), you will find [[BoundTarget]], [[BoundArgs]] and [[BoundThis]]. They indicate that inc is a bound function first of all, and also it tells you all about it: that is wraps Sum function, binds first argument with value 1 and passes null as this.

Copy link

just fwiw, we'll probably post this somewhere more permanent. html5rocks, chromium blog, my blog.. somewhere..

Copy link

feedback to integrate:

  • what is s ? ('hello')
  • “Who else has internal properties? It's bound functions.”
  • [[BoundTarget]], [[BoundArgs]] and [[BoundThis]] seem nice though
  • also using a String object is an odd example, it might be nice to show a real example
  • a, b, c -> use real names!

Copy link

  • "have you ever wanted to know what this value or arguments a bound function is bound to? well CHECK THIS OUT"

Copy link

  • Lets use something more dynamic than a string in our watch expression.

also cc @ecmanaut and @simonsarris on this if you want to take a peek.

Copy link

Copy link

Garbee commented Nov 29, 2012 Seems like a nice place to post it to me, might need a new section though. Even have it in WPD once we figure out where dev tool stuff will go down the road.

Copy link

@paulirish, I'd like to move this to the docs after a few more edits if that works for you. Would you be down with that? :)

Copy link

Copy link

gyfnice commented Jul 11, 2013

very Nice!!

Copy link

a good job!

Copy link


Copy link

The second statement calls function B (b) that returns an array item. Why not function B(1)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment