Output logging level for build

[eddiemonge]

By default (and I haven't found a way to change), the output from npm run build is very verbose and mostly unnecessary (after the first run). It would be nice if there was a way to specify log level to turn it off.

The logging is output here: https://github.com/facebook/create-react-app/blob/7b1a32be6ec9f99a6c9a3c66813f3ac09c4736b9/packages/react-scripts/scripts/build.js#L85-L123

[andriijas]

Not following your requirement here. Exactly what is it you want less of in subsequent builds that you dont consider useful?

[eddiemonge]

Pretty much all the stuff it outputs. I definitely don't need hosting info, especially not every time I build. I don't really need file size info. While it's a nice statistic, its doesn't really add much value other than a "look how efficient the tool is".

[andriijas]

If you are on a nixy env you can pipe the output to /dev/null

[eddiemonge]

That's not the point. And that's not even a good suggestion. Doing that means I won't get any of the output. That is not ideal.

The hosting message should not probably not be in the build message but rather should be shown on project creation.

The file size could be shown if a verbose flag is passed.

Please reconsider closing this issue

[lukasgjetting]

@andriijas I run yarn build in a GIT post-receive hook. In that scenario, I don't think it's necessary to print the filesizes nor the hosting info (maybe not even the eslint warnings).

However, errors should still be printed (which is why piping to /dev/null doesn't work).

Maybe a --silent arg?

create-react-app/packages/react-scripts/build.js

 const argv = process.argv.slice(2);
 const writeStatsJson = argv.indexOf('--stats') !== -1;
+const silent = argv.indexOf('--silent') !== -1;

...

+      if(!silent) {
         console.log('File sizes after gzip:\n');
         printFileSizesAfterBuild(
           stats,
           previousFileSizes,
           paths.appBuild,
           WARN_AFTER_BUNDLE_GZIP_SIZE,
           WARN_AFTER_CHUNK_GZIP_SIZE
         );
         console.log(); 

         const appPackage = require(paths.appPackageJson);
         const publicUrl = paths.publicUrl;
         const publicPath = config.output.publicPath;
         const buildFolder = path.relative(process.cwd(), paths.appBuild);
         printHostingInstructions(
           appPackage,
           publicUrl,
           publicPath,
           buildFolder,
           useYarn
         );
+      }

[andriijas]

Submit a pr?

[lukasgjetting]

@andriijas Yup (#5429)

However, the AppVeyor build fails on something seemingly unrelated:

Failed to compile.
.\src\App.js
You attempted to import ../sample which falls outside of the project src/ directory. Relative imports outside of src/ are not supported.
You can either move it inside src/, or add a symlink to it from project's node_modules/.

It seems to happen to most new pull requests (some of them only run through Travis, though?). Do you know what's happening?