Why isn't webpack_compile_output enabled by default?

[kevinnio]

How you doing guys.

I was wondering why isn't webpack_compile_output enabled by default. If webpack fails to compile your bundles you won't see anything unless you enable it. Compiling issues are so commonplace when working on code or deploying that it doesn't make sense to me to have all webpack output stripped out by default.

Would you guys consider having webpack_compile_output enabled by default? I think most people would benefit from that. Of course some devs may not want to see all the webpack output every time they do a change and refresh the browser, but they can always disable it.

[jakeNiemiec]

Seeing how many 👍's #955 (comment) has, I think the users have spoken. Can someone create a PR?

webpacker/lib/install/config/webpacker.yml

Line 10 in 336077d

webpack_compile_output: false

---

A different aspect of this that I am keen to revisit is #1834 by @yvbeek. I think errorDetails should also be true by default when in development:

webpacker/package/environments/development.js

Line 43 in c4cf2e9

errorDetails: false,

[LuanGB]

@jakeNiemiec just created this simple pr to add this modifications. Let me know if anything else is needed...

[kevinnio]

LGTM @LuanGB. Let's see what the maintainers have to say.

[yvbeek]

@jakeNiemiec @LuanGB are you guys using TypeScript with Webpacker?
It just seems to output so much info when errorDetails is true

Perhaps we can turn it back on for non-TypeScript projects?
Or can we somehow reduce the output to only the actual errors, not all that plugin noise?

If this is causing issues for a lot of people, please do set it to true by default.
However it would be nice to reduce all that output to useful information.

[jakeNiemiec]

@yvbeek are you guys using TypeScript with Webpacker?

No

Or can we somehow reduce the output to only the actual errors, not all that plugin noise?

modules is still false in the PR, so this should not be an issue.

It just seems to output so much info when errorDetails is true

This only sets the default. We want users who are inexperienced with webpacker to have easy access to errors. With #955, #2143 (comment), #2276, and others in mind, it seems like a better idea to default this to true for new installs. You can always change this in your webpacker.yml.

Annoying errors are better to have than silent errors. (and are easier to fix!)

[Air-Craft]

I've just been banging my head at webpacker not injecting my imported CSS in rails 6. Enabling this option and restarting seems to have solved it. Might I ask what the advantage to having it off is?

[h0jeZvgoxFepBQ2C]

I set it to true, but still don't get any log output?