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

Clearing console makes it impossible to debug webpack config #89

Closed
aem opened this issue Apr 2, 2017 · 6 comments
Closed

Clearing console makes it impossible to debug webpack config #89

aem opened this issue Apr 2, 2017 · 6 comments

Comments

@aem
Copy link

aem commented Apr 2, 2017

Current Behavior

Any console.logs in webpack.haul.js are cleared immediately

Expected 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 PR

Your Environment

software version
Haul 0.2.1
react-native 0.42.3
node 7.7.4
npm or yarn yarn 0.21.3
@satya164
Copy link
Member

satya164 commented Apr 2, 2017

It's not cleared. Just moved up. You can scroll up to see old logs

@aem
Copy link
Author

aem commented Apr 3, 2017

upon further investigation, it appears that you're correct only if you're using bash as your shell. in zsh it actually clears the contents

@grabbou
Copy link
Member

grabbou commented Apr 3, 2017

What is the terminal app you are using? I can experience the same behaviour when running zsh and Hyper. Switching to stock Terminal works as expected.

If yes, feel free to close and report here vercel/hyper#1662

@aem
Copy link
Author

aem commented Apr 3, 2017

zsh in Terminal.app and zsh in the integrated IntelliJ terminal

@aem
Copy link
Author

aem commented Apr 3, 2017

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

@grabbou
Copy link
Member

grabbou commented Apr 3, 2017

It's probably related issue to what Hyper is having.

@grabbou grabbou closed this as completed Apr 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants