Nap is attached to global scope.

[monokrome]

As avoiding globals is a generally good practice, it'd make more sense to attach the nap object to env.helpers such as done in wintersmith-livereload.

[aularon]

I will look into this today. Thanks!

[monokrome]

Thank you!

[aularon]

Apparently env.helpers is not exposed inside templates, so for now I am sticking with the ugly global. solution 😞

[aularon]

And the latest jade totally hides global objects inside template, which is good, but now one has to call global.nap, I am looking into wintersmith on how to add a function/object to be accessible from within views.

[aularon]

Found a method utilizing wintersmith's env.locals, works like a charm! 😎

[monokrome]

env.helpers is exposed in templates. If it wasn't, that livereload plugin wouldn't work. It creates a function that injects a script into the HTML.

[aularon]

mmm I see, but you have to call it as !{ env.helpers.livereload() }, instead of directly as in != nap.css('main').
The env.locals is exposed in templates so one can directly call != nap.css('main'), I believe this is better.

I am going to open an issue on wintersmith asking whether using env.locals this way is good, and won't break in the future.

[monokrome]

The env.locals is not as good, because there is potential that a specific template can override them. The env.locals variable (if I understand correctly) will potentially be overridden with context data from the template being rendered. However, env.helpers doesn't have this issue.

For instance, if I had a template:

jade.compileClient('something, { locals: { nap: true } });

The nap variable would now be set to true at the template level, but this wouldn't be the case with env.helpers. I specifically referenced the LiveReload plugin, because it is written by the same person who wrote WinterSmith itself. I expect that is the expected use case for WinterSmith due to this, but may be assuming too much?

The issue here is that locals is intended for transient template variables, while it makes more sense from a development standpoint for things like nap to be accessible in the env via something like env.helpers.

[aularon]

Sorry for the late reply, I am having electricity blackouts where I live that I am barely keeping up with my TODOs.

I will make it as an option in the config object, if set to true, it will make it to env.locals. It will be false be default (So it will be only present in env.helpers by default).