Ivan Demidov

@ctf0 There were no movements, maybe you can do it?

@jonathantneal Hi, Thank you for your interest, it is very important for us and we welcome any suggestions and are ready for action. > I’d love to see these features...

Hello, everything has been available for a long time ```js const fs = require('fs') const posthtml = require('posthtml') const html = fs.readFileSync('index.html', 'utf-8') const plugins = [] const options =...

plugins do not need to know about each other as well as the general process does not need to know anything about plugins

> So is it possible for the plugin to change the posthtml's configuration? like any value in an object

You can always save the value in your plugin scope so as not to affect the rest ```js const opt = {...tree.options} ```

Put the processor, it doesn't owe anything, it does its job. `htmlnano` can rely on `posthtml` options. Why does htmlnano want to change the value of options?

Let's do this, here's an example, it works as you expect, what feature needs to be implemented? ```js const posthtml = require('posthtml') const html = ` ` const plugins =...

I also parry with a quote > > So is it possible for the plugin to change the posthtml's configuration? > > like any value in an object You can...

Don't think about other plugins, htmlnano will always be the last one. You cannot influence the result previous or subsequent after your plugin. Recommend installing your plugin last.