node [file.js] produce different result with run browser, and nodejs .editor

Question

I have below piece of code in test.js file

   function foo(){
      console.log(this.bar);
    }

    var bar = "bar1";
    var obj = {bar: "bar2"};

    foo();
    foo.call(obj);

when I run by 'node test.js', I got result

undefined 
bar2

when I run in node .editor, I got result

bar1 
bar2

I think the second result is right, but what is wrong with the first way? cuz I always do the first way.

what are the differences between them?

Here is your answer, stackoverflow.com/questions/34967530/… — Janith
– Janith, Commented Sep 15, 2018 at 4:06

Janith · Accepted Answer · 2018-09-15 04:10:42Z

1

In simple terms when you run the your code using node test.js, Node JS will require('test.js') to run it. But when you are using the REPL mode, code you enter will execute directly in the REPL.

When using require, the variables on your test.js won't bind as global variables. So cannot access like this.bar

answered Sep 15, 2018 at 4:10

Janith

2,92818 silver badges28 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

B.W · Accepted Answer · 2018-09-15 03:55:32Z

0

I think when using 'node test.js', node create a wrapper for test.js code, so there is no global variable bar.

while in .edit way, there is a variable bar defined in global scope.

answered Sep 15, 2018 at 3:55

B.W

771 silver badge5 bronze badges

Collectives™ on Stack Overflow

node [file.js] produce different result with run browser, and nodejs .editor

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related