PM2 ecosystem config logs not working on windows

What's going wrong?

Setting out_file and error_file doesn't have any effect on windows, while it works on linux (Ubuntu 20)

How could we reproduce this issue?

Create such a config file ecosystem.config.js

const {join} = require("path");

const logsFolder = join(__dirname, "dist", "logs");

module.exports = {
    apps: [
        {
            name: "my-awesome-server",
            script: "npm --start", // build and start server
            out_file: join(logsFolder, "/out.log"),
            error_file: join(logsFolder, "error.log"),
            cron_restart: "0 0 * * *",
            env: {
                PORT: 3000,
                HTTPS_PORT: 5000,
                NODE_ENV: "development",
                DB_HOST: ["localhost", "82.223.83.177"][1]
            },
            env_production: {
                PORT: 3000,
                HTTPS_PORT: 5000,
                NODE_ENV: "production",
                DB_HOST: "localhost"
            }
        }
    ]
};

Supporting information

Using PM2 v 5.2.2 on Windows 11

$ pm2 report

Not pasting this because it only showed stuff like start app, or process killed...nothing relevant at all...

Start with the supplied ecosystem.config.js and reproduce the behavior on Windows 11 using PM2 v5.2.2, comparing out_file and error_file with the working Ubuntu case. Use pm2 report and the process output to narrow down why the configured log paths are ignored; done means both configured files receive the expected output and errors on Windows.