Error on new project
See original GitHub issueCurrent Behavior
On creating a new project with haul the app shows error screen on launch
Steps to reproduce
- Create new react-native project (react-native init)
- Add haul
yarn add --dev haul - Start haul server
yarn run haul - Run the app in the iOS simulator
react-native run-ios
Expected Behavior
The app should run
Haul Configuration (webpack.haul.js)
module.exports = ({ platform }) => ({
entry: `./index.js`,
});
Your Environment
Mac OS High Sierra, iOS 11.1 simulator iPhone 6
| software | version |
|---|---|
| Haul | ^1.0.0-beta.10 |
| react-native | 0.50.4 |
| node | 8.7.0 |
| npm or yarn | yarn 1.3.2, npm 5.4.2 |
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
compilation error while creating new project. 2021.1.20f1
I downloaded Unity 2021.1.20f1 and tried to create a new project, but then a error pops up saying "The project you are opening...
Read more >Getting an error while creating a new project in VS2019
After integration with ClearCase, when we create a new project, we are getting a error message dialog of Visual Studio. The error says...
Read more >Compile error in new project - Unity Forum
I started a new project in 2020LTS and get 2 errors when the project is first built, before I add any assets or...
Read more >Unity error immediately after creating a new Project
Go into your Unity Package Manager and find the Visual Studio Code package. Click 'see all versions'. Change the versions and try ...
Read more >Error when trying to add a new Project task or move current ...
When in Project, if a new Project task is added or if tasks are moved, a generic error is seen: Unexpected error encountered....
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

This is a bug related to Webpack. I’m still searching for a satisfactory solution. As a walk around you have to downgrade to Webpack 3.8.x.
This is related PR into Webpack itself: https://github.com/webpack/webpack/pull/5862
you can just pin to an older version of webpack for now
edit: just noticed you already did, hah