-
Notifications
You must be signed in to change notification settings - Fork 194
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
Clearing console makes it impossible to debug webpack config #89
Comments
It's not cleared. Just moved up. You can scroll up to see old logs |
upon further investigation, it appears that you're correct only if you're using |
What is the terminal app you are using? I can experience the same behaviour when running If yes, feel free to close and report here vercel/hyper#1662 |
zsh in Terminal.app and zsh in the integrated IntelliJ terminal |
actually, scratch that. i thought i had tested in Terminal, but i guess only in intellij. Looks more like a bug with IntelliJ then. sorry for the noise |
It's probably related issue to what |
Current Behavior
Any
console.log
s inwebpack.haul.js
are cleared immediatelyExpected Behavior
Debugging the webpack config should be possible. At the moment there's no way to check if, say for example, you're extending the default config, the output object is actually what you want it to be.
Possibly a
--no-clear
option would be helpful, default to the clean console approach but allow override if necessary? I'd be happy to take care of this if you're looking for a PRYour Environment
The text was updated successfully, but these errors were encountered: