You get no output at all? This is very strange, since there are no system calls involved here. Could you try a simple JS file with console.log("test");, please?

When did it stop working? When you upgraded Node.js or on some GopherJS version?

// commandline sequence with Node 4.2.1:

c:\Go\work\src\github.com\rusco\dummy>node -v
v4.2.1

c:\Go\work\src\github.com\rusco\dummy>type main.go

// +build js

package main

import "github.com/gopherjs/gopherjs/js"

func log(i ...interface{}) {
        js.Global.Get("console").Call("log", i...)
}

func main() {
        print("print message")
        log("log message")
}

c:\Go\work\src\github.com\rusco\dummy>gopherjs build main.go

c:\Go\work\src\github.com\rusco\dummy>node main.js
print message
log message

c:\Go\work\src\github.com\rusco\dummy>gopherjs run main.go

c:\Go\work\src\github.com\rusco\dummy>node

console.log("test");
test
undefined
.exit

c:\Go\work\src\github.com\rusco\dummy>

//Just for curiosity I downgraded node to v0.12.7 with sourcemap support and it looks the same. Unfortunately I have no clue since when this happend, but I suppose within the last 2 months.
For now I propose to wait for confirmation from other windows users.

Please put a panic in there to see if the code is running at all.

Looks like not.

node main.js -> throws the exception
gopherjs run main.go -> nothing

Hmm that's strange. You could try 151315c. That's before the sourcemap change.

Looks the same. Let's wait until some other windows user confirms this, I can live with running node manually.

This may be resolved, as of #1111 , but it would be good to confirm.