Bad Error messages
See original GitHub issueCurrent Behavior
it’s giving non understandable error messages
Helpful and easy to understand error messages mentioned in readme, but it’s no longer correct
Expected Behavior
Should show understandable error message, like it’s showing rn-packager

Haul Configuration (webpack.haul.js)
Configuration didn’t changed
Your Environment
| software | version |
|---|---|
| Haul | latest |
| react-native | latest |
| node | 7.5.1 |
| npm or yarn | 4.1. |
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Error Messages: Examples, Best Practices & Common Mistakes
4 common mistakes with error messages · 1. Ambiguity · 2. Condescending language/blaming the user · 3. Poor placement of error messages ·...
Read more >How bad error messages are harming your users - UX Collective
Be explicit and indicate something has gone wrong · Include messages on same screen as where the error occurred · Include the product...
Read more >Best 10 Examples And Guidelines For Error Messages
Here are ten basic guidelines to help you create the most effective error messaging for your users. Click here to see all of...
Read more >Hostile Patterns in Error Messages - Nielsen Norman Group
Premature error messages, aggressively styled fields, and unnecessarily disruptive system-status messages feel bad-mannered and increase ...
Read more >Bad error messages - SlideShare
2. What is a "bad error message?" Simply put, a bad error message is a dialog box or error that doesn't make sense...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Experiencing similar issue.
@itaym2 thanks for triaging this, closing then 😃