question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Not showing webpack compilation warnings

See original GitHub issue

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions.

@angular/cli: 1.3.0-rc.3
node: 6.11.1
os: win32 x64
@angular/animations: 4.3.1
@angular/cdk: 2.0.0-beta.8
@angular/common: 4.3.1
@angular/compiler: 4.3.1
@angular/core: 4.3.1
@angular/forms: 4.3.1
@angular/http: 4.3.1
@angular/material: 2.0.0-beta.8
@angular/platform-browser: 4.3.1
@angular/platform-browser-dynamic: 4.3.1
@angular/platform-server: 4.3.1
@angular/router: 4.3.1
@angular/service-worker: 1.0.0-beta.16
@angular/cli: 1.3.0-rc.3
@angular/compiler-cli: 4.3.1

Repro steps.

After upgrading to 1.3.0-rc.3 and doing some bad things, ng serve outputs:

webpack: Compiling...
webpack: Compiled with warnings.

But no warnings are printed 😞

(I encountered the issue with there changes, but any changes creating warnings should do.)

The log given by the failure.

N/A

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Comments:7 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
Matmo10commented, Aug 3, 2017

@filipesilva @hansl Could this be made configurable at all?

I have lots of the fake errors stemming from https://github.com/angular/angular-cli/issues/2034, and I actually enjoyed having the warning output rather limited.

Not only did you guys bring back the first line of the warnings (how it use to be), but you also added the whole stack traces as well. So now I have a giant wall of stack traces every time I make a change.

0reactions
angular-automatic-lock-bot[bot]commented, Sep 7, 2019

This issue has been automatically locked due to inactivity. Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

Read more comments on GitHub >

github_iconTop Results From Across the Web

webpack compiles with warnings, but the warning messages ...
I am using the latest versions of Node, NPM, webpack and the UglifyJS webpack plugin. I am running this on Windows. I get...
Read more >
Dev Server does not always show webpack config compilation ...
I debugged react-scripts in the following way and found the cause of the project not running. The cause is that the webpack config.output....
Read more >
Change the way webpack compile warnings are surfaced
Configure some way to surface these warnings with danger or some allowed-to-fail job which inspects the webpack output to ensure compile issues ...
Read more >
Command Line Interface - webpack
webpack-cli offers a variety of commands to make working with webpack easier. ... --no-stats, Disables any compilation stats emitted by webpack.
Read more >
webpack.Compilation.warnings JavaScript and Node.js code ...
warnings (Showing top 4 results out of 315). Tabnine vs. GitHub Copilot. Why developers prefer Tabnine over GitHub Copilot?
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found