Skip to content
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

Webpack config stats has no effect #204

Closed
svengau opened this issue Nov 25, 2019 · 6 comments
Closed

Webpack config stats has no effect #204

svengau opened this issue Nov 25, 2019 · 6 comments
Labels

Comments

@svengau
Copy link
Contributor

svengau commented Nov 25, 2019

Hi,

the stats config in webpack could not be configured, because it's hardcoded in the code:


console.log(stats.toString({ color: true }));

For example, I would like to remove some noisy warnings with the following config, but it's not possible:

  stats: {
    warningsFilter: [
      /Critical dependency: the request of a dependency is an expression/,
      /Critical dependency: require function is used in a way in which dependencies cannot be statically extracted/
    ],
  },

Thanks.

[edit]: Here is the list of all parameters of the toString(...) function.

@svengau
Copy link
Contributor Author

svengau commented Nov 25, 2019

I've proposed a PR: #205

@svengau svengau changed the title Webpack config stat has no effect Webpack config stats has no effect Nov 25, 2019
@kevinmarrec
Copy link

Just encountered the same issue, I wanted to set stats.entrypoints to false but doesn't seem indeed possible.

@svengau
Copy link
Contributor Author

svengau commented Jan 8, 2020

Hi @markus-willems and sorry to bother you. I'm not sure about the issue review workflow on this repo. Would it be possible to have a feedback on this issue from the Netlify team ? Thanks.

@markus-willems
Copy link
Contributor

markus-willems commented Jan 8, 2020

Hey @svengau. Don't worry, all good! Unfortunately, I am not affiliated with the fine people of Netlify. That'd be Shawn (@sw-yx) for example. Good luck with your issue.

@swyxio
Copy link
Contributor

swyxio commented Jan 13, 2020

thanks for the ping. i dont really maintain this anymore. i'll merge this tho

@stale
Copy link

stale bot commented Mar 13, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the stale label Mar 13, 2020
@stale stale bot closed this as completed Mar 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants