Logger not loading after conversion to ES module about fastify-cli HOT 3 CLOSED

I've encountered the same problem today, loading aditional logger configuration file seems not supported in ES module projects(with type: "module" in nearest package.json) yet.

Here is how I fixed the logger customizing issue, instead of specifying an external logger configuration file, we could set FastifyServerOptions in our app.js/app.ts file.

1. If your project was automatically generated by fastify-cli with it's template, you should find the code like below in your app.js or app.ts file.

app.ts (in my ts project)

// Pass --options via CLI arguments in command to enable these options.
const options: AppOptions = {
    logger: {
        level: 'info',
        customLevels: {
            test: 99
        }
    }
}

or app.js

// Pass --options via CLI arguments in command to enable these options.
module.exports.options = {
  logger: {
     level: 'info',
}

2. Append -o flag in your fastify-cli command, eg. fastify start -o -P app.js

Wish this could help you with your logger issue.

from fastify-cli.

Thanks for your solution, unfortunately my multi-stream-logger.js is rather complex, I import several libraries there in order to log to console and file system simultaneously and perform log rotation of the written log files. So it's not doable via options.

My current temporary solution is I simply use this one file as CommonJS module, the rest of the files in my project are ES modules now. As the ".cjs" file extension didn't work, I created a new folder and put the multi-stream-logger.js in there together with a new package.json file with the following content (only this one line):

{ "type": "commonjs" }
That way all files in that folder are interpreted as CommonJS modules and the multi-stream-logger.js import worked.

from fastify-cli.

Just ran into this same issue. Our start command uses the Fastify CLI to load a specific logging module, which is a CJS file. However, it seems like the fastify cli is rewriting the filename to assume a ".js" extension? So then Node thinks it needs to be a module, but is being loaded by a synchronous, CommonJS require(), and thus it doesn't work.

from fastify-cli.