added debug mode emitting underlying configuration

[FND]

this might be useful for debugging, but also for recreating the
corresponding configuration elsewhere (e.g. test cases, migrating away
from faucet etc.)

(sample below)

use cases:

• @tbse had expressed apprehension WRT potential lock-in, understandably arguing it should be possible to migrate away from faucet (which is perfectly in line with faucet's philosophy). However, turns out directly generating Rollup/Babel configuration files isn't trivial because the programmatic APIs are (slightly) different and because serializing our configuration object afterwards would be unhelpful WRT plugin functions and their respective configuration. So instead we're emitting our configuration as we generate it, allowing informed users to manually-but-easily recreate it elsewhere.
• When playing with Svelte, but also when creating minimal test cases, I often found myself arduously recreating Rollup configuration that essentially looked the same as faucet's. This should simplify that process somewhat.

sample output

$ FAUCET_ENV=DEBUG npm run compile
> faucet --compact

[DEBUG] ESNext transpilation
[DEBUG] JSX transpilation
transpiling JavaScript for IE 11
[DEBUG] transpiler plugin: @babel/plugin-transform-react-jsx {
    "pragma": "createElement"
}
[DEBUG] plugin: rollup-plugin-babel {
    "exclude": [
        "node_modules/promiscuous/**",
        "node_modules/document-register-element/**"
    ],
    "presets": [
        [
            "@babel/preset-env",
            {
                "modules": false,
                "targets": {
                    "browsers": [
                        "IE 11"
                    ]
                }
            }
        ]
    ],
    "plugins": [
        [
            "@babel/plugin-transform-react-jsx",
            {
                "pragma": "createElement"
            }
        ]
    ]
}
[DEBUG] plugin: rollup-plugin-node-resolve {
    "mainFields": [
        "module",
        "jsnext:main",
        "main"
    ],
    "extensions": [
        ".js",
        ".jsx"
    ]
}
[DEBUG] plugin: rollup-plugin-commonjs {
    "include": "node_modules/**"
}
[DEBUG] plugin: rollup-plugin-terser {
    "compress": false,
    "mangle": false
}
[DEBUG] Rollup settings: {
    "sourcemap": false,
    "compact": true,
    "plugins": [
        {
            "name": "babel"
        },
        {
            "name": "node-resolve"
        },
        {
            "name": "commonjs"
        },
        {
            "name": "terser"
        }
    ],
    "format": "iife"
}

[FND]

JSON.stringify avoids [Object] being emitted for nested objects

it also happens to filter out plugin functions, which might be good or bad

[FND]

I assume we agree?

[moonglum]

Yes.

[FND]

this allows avoiding unnecessary computation by making it conditional:

if(DEBUG) {
    debug(new CryptoMiner());
}

(more likely to be used as a one-liner though: DEBUG && debug(…))

[moonglum]

Interesting approach 👌 @tbse would that satisfy your use case?