-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on build #31
Comments
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 pnpm install -D pino-webpack-plugin // webpack.config.js
const { PinoWebpackPlugin } = require('pino-webpack-plugin');
module.exports = {
// ...
plugins: [
// ...
new PinoWebpackPlugin({ transports: ['pino-pretty'] }),
],
} 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. // package.json
{
...
"pnpm": {
"overrides": {
"webpack": "^5.78.0"
}
}
} Maybe I will point out this in the README for the next release, Thanks. |
Works perfectly, thanks @kenso312 ! |
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: