Nunjuck plugin constructor options

[fserb]

This pipes the options from pluginOptions to the Nunjuck's environment constructor.

[oscarotero]

Nunjucks is not using any option already, so this change doesn't have any effect.

[fserb]

I'm not sure what you mean. This allows the user to pass options to the nunjucks, like those:

const site = lume({ }, {
  nunjucks: {
    trimBlocks: true
  }
});

[oscarotero]

Ah, got it. I see that you are passing the options in new nunjucks.Environment.

Ok, before merging, I propose two changes:

1. The config object passed to plugins isn't only to configure nunjucks but the whole plugin. This includes the file extensions to which the plugin will be applied and opens the door to other future options. If you see other extensions like terser or markdown, there's a options key containing the options for the terser and markdown-it library. For nunjucks, we should do the same:

const site = lume({ }, {
  nunjucks: {
    options: {
      trimBlocks: true
    }
  }
});

2. You're passing userOptions to NunjucksEngine instead the options variable (result of merging user and default options), and specifically, options.options (Only the options for the template engine): const nunjucksEngine = new NunjucksEngine(site, options.options);

[fserb]

Done. I think. As I understood both requests were kinda the same? Please let me know.

[oscarotero]

Perfect. Thanks!