How to debug Plugins?

[ishu3101]

How do you debug plugins when you are developing plugins?

[Semigradsky]

I just insert console.log 😄

[ishu3101]

But then where do you see the console log?

[notatestuser]

Press F12 - it'll open devtools.

[ishu3101]

Pressing F12 does nothing.

[notatestuser]

Do you have afaaeed?

[ishu3101]

No was using v0.0.2-rc4, Updated to the latest release which is v0.0.3.

[KennethWussmann]

Better use PluginContext.Logger.log("message"); as mentioned here.

[ishu3101]

I have noticed that using console.log causes the plugin to break in v0.0.3 but in v0.0.2-rc4 it did not cause any problems

[sethxd]

I was having this same issue trying to use console.log. Fixed it by including this line just inside module.exports: const logger = pluginContext.logger

And calling it like this: logger.log("Hello world!")

[likerRr]

Hey everyone.

Sometimes I face an issue when DevTools shows just Object{} without any properties (except native prototype) for my objects or even null at all (but properties exist and they're accessible). Can't provide an example for the first case, because it doesn't work on simple code, but here is a simple version of the second case (lodash should be installed):

let _ = require('lodash');

module.exports = (context) => {
  return {
    startup() {
      context.logger.log(_); // null
      context.logger.log(_.identity(2)); // 2
    }
  };
};

What's the matter?

[likerRr]

@appetizermonster have ideas? ^^^

[appetizermonster]

There is no advanced way to debug plugins for now. we should make it.
not in docs, but you can use console.log in the plugin if you launch hain on commandline prompt. (but you should remove them in the production)
so it may be helpful for debugging.

[cpriest]

I have v0.5.2 which should include afaaeed but F12 does not do anything, F5 does however work which I see that commit also had some code in for. Is F12 expected to be working right now?

[appetizermonster]

@cpriest I'll take a look at it, thanks for the reporting

[abinadi]

I had the same issue as @cpriest. I'm on v0.5.2 and F12 does nothing. Not sure if it is pertinent, but I used the pre-built binary.

[DanielFallon]

F12 should be fixed now. F12's handler was firing, but the dev tools weren't being opened properly

see #212