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
Disable in CI #109
Comments
Yes. it's possible. const webpack = require('webpack');
const WebpackBar = require('webpackbar');
module.exports = {
context: path.resolve(__dirname),
devtool: 'source-map',
entry: './entry.js',
output: {
filename: './output.js',
path: path.resolve(__dirname)
},
plugins: [
...(process.env.CI === '1' ? [] : [ new WebpackBar() ])
]
}; |
Is there another solution to do not have that many lines without disabled it ? |
The only line that you need is this one: ...(process.env.CI === '1' ? [] : [ new WebpackBar() ]) Everything else is part of your Webpack config as usual. I've added it there to showcase how it would look like. |
Yeah that disable the utility, and we don’t want to disable we want to have that working as usual but not generating that many lines. Do you know how to tell the ci to reuse the lines effectively? |
Unfortunately, I don’t see the point of having that plug-in enabled in CI. This is a plug-in for feedback mostly during development. your CI output is just a stream of logs that don’t behave as exactly as your local terminal during development. |
We follow the ci integrations in productions sometimes and we want to see the progress of the build that’s why. I try many things but no one worked |
Is that possible to disable webpackbar in CI with process.env?
The text was updated successfully, but these errors were encountered: