You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report, it should be a known issue and the reason is because of pino-pretty. I do not point out that in the README is because I expect we will not use pino-pretty in a production build, so I assume you have NODE_ENV=production in the .env or docker env by default. But for some reason if you still want to use pino-pretty in the production, you can use pino-webpack-plugin to solve this, just simply install it and add some lines the webpack.config.js.
I tested in the v2.2.1, seems upgraded packages make the webpack version not sync and break the build, so I have to force override the version to make it work. No this step requires for v2.2.0.
Steps to reproduce
pnpm build && pnpm start
Expected behavior
Build succeed
Current behavior
Hi there,
Thank you for this great boilerplate ! Been working on it all day yesterday, but had a quack when I tried to build the project.
I tried building from the repo without any modification and had the same issue.
Looks like an issue with PINO. I tried many things to fix it and made it with on of the following:
NODE_ENV=production
toscript.start
in package.jsonAny better way to fix it ?
Thanks,
Tim
Node.js version
18
In which operating systems have you tested?
Other
No response
The text was updated successfully, but these errors were encountered: