Daniel Ruf

> If this is intentional behaviour, it would be neat if we had a flag to override it. Yes, see the `ignoreCustomComments` setting, that you can change. https://github.com/terser/html-minifier-terser?tab=readme-ov-file#options-quick-reference ignoreCustomComments |...

Ah I see now. > Renamed the customCode section of the options config to the customLogic in order to avoid confusion with the existing customCode property within.

After further checks it seems the documentation is outdated. Instead of `info.data` it should be `info.result`. After fixing that, it says `Error: ENOENT: no such file or directory, open '...\public\resources.json'`....

@PaulDalek when I have this config, I get the error: ``` customLogic: { allowCodeExecution: true, allowFileResources: false, customCode: false, callback: false, resources: false, loadConfig: false, createConfig: false }, ``` When...

So far I have moved to the CLI where the issue does not exist with the same parameters. So I guess there is some inconsistence between the NodeJS module and...

No ESM support in pkg yet: * https://github.com/vercel/pkg/issues/1404#issuecomment-977848391 * https://github.com/yao-pkg/pkg/issues/16 Checking how to resolve that.

Got it working, as CommonJS compiled with rollup and as static binary with pkg: ``` npm run build pkg . node cli.cjs --enableServer 1 ./highcharts-export-server-linux --enableServer 1 ``` Minimal changes...

The following code should probably not be used then, because it fills the tmp folder with every execution. ```js const RANDOM_PID = node_crypto.randomBytes(64).toString('base64url'); const PUPPETEER_DIR = path.join('tmp', `puppeteer-${RANDOM_PID}`); ``` https://github.com/highcharts/node-export-server/blob/c8a360ab8e8bdf5cb7f6566040b5afeab0589a74/lib/browser.js#L21-L27...

@cvasseng can [this logic](https://github.com/highcharts/node-export-server/issues/543#issuecomment-2241198795) be removed again and a new v3 patch release done?

I would like to use the CLI of v4 as statically compiled binary. Because this way we can get rid of NodeJS as separate dependency on servers in production. Currently...