🐛 `console.log` not working in player.js

Environment

  System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
    Memory: 8.48 GB / 15.86 GB
  Binaries:
    Yarn: 1.5.1 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 5.7.1 - C:\Program Files\nodejs\npm.CMD
  Virtualization:
    Docker: 18.03.0 - C:\Program Files\Docker\Docker\Resources\bin\docker.EXE
  IDEs:
    VSCode: 1.23.1 - C:\Program Files\Microsoft VS Code\bin\code.CMD
  Languages:
    Bash: 4.4.12 - C:\Program Files\Git\usr\bin\bash.EXE
    Python: 2.7.14 - /c/Python27/python
  Browsers:
    Edge: 42.17666.1000.0
    Internet Explorer: 11.0.17666.1000

Steps to reproduce

1. Install warriorjs

• npm i -g warriorjs

1. Bootstrap with warriorjs

• warriorjs (follow default config)

1. Open Player.js and add a console.log('hello') statement in the playTurn method

• playTurn () { console.log('Hello World'); }

1. Run warriorjs

• warriorjs (select your character to run)

1. The log is not displayed

Expected Behavior

All console statements should be displayed in the output (or at least logged to a file).

Actual Behavior

No console statements display.

Additional Notes

So far I think the issue comes from running in a new vm context. That call happens here: https://github.com/olistic/warriorjs/blob/master/packages/warriorjs-core/src/PlayerLoader.js#L23

And finally, this is a really cool project. Thanks to everyone for the great work so far!

[olistic]

WarriorJS v0.3.0 includes a think ability that can be used as an alternative for console.log. It’s not perfect yet, but I think it’s good enough for now. Let me know if you have any feedback, I’m closing this ticket now.

[pajtai]

I found using the debugger super helpful.

It’s easiest with a local npm install:

npm i @warriorjs/cli

and then add an index.js as follows

'use strict';

require('@warriorjs/cli/bin/warriorjs');

now you can debug with:

node --inspect-brk index.js - just drop a debugger in player.js and play around with the commands.