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.

[Bug] Basic Template react-static build hangs at "Bundling App"

See original GitHub issue

Bug

I have two React Static sites which have both run into the same problem where images on the home page are coming up as 404 errors in the console. Neither of these codebases have been updated in the past couple months and have only been rebuilt with webhooks periodically. When I went to investigate why this was happening, I realized that react-static build was hanging at “Bundling App” and these missing images were getting placed into the artifacts folder.

I started a fresh basic template but react-static build is still hanging at “Bundling App”.

I’ve tried installing/uninstalling different versions of npm/yarn and React Static but have had no luck. I’ve also tried --debug and --dev flags with react-static build.

This issue is similar to a previous issue although the basic template doesn’t seem to run into “TypeError: Property value expected type of string but got null” (I get that error intermittently with other my other React Static projects).

Any help with this would be greatly appreciated.

Environment

System: OS: Windows 10 CPU: (4) x64 Intel® Core™ i7-7600U CPU @ 2.80GHz Memory: 6.61 GB / 15.84 GB Binaries: Node: 10.16.0 - C:\Program Files\nodejs\node.EXE Yarn: 1.17.3 - C:\Program Files (x86)\Yarn\bin\yarn.CMD npm: 6.11.3 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: 44.18362.329.0 Internet Explorer: 11.0.18362.1

Node: 10.16.0 React Static: 7.2.2

Steps to Reproduce the problem

npm install -g react-static
react-static create test
select basic template
react-static build

Expected Behavior

Successful build

Issue Analytics

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

Top GitHub Comments

1reaction

Robp773commented, Sep 26, 2019

Interesting! That is a completely new thing.

Alright. At least you can now have something workable with an initial crash. This is on my top priority list.

Sounds good, I’m going to close this issue since the --debug flag does work and that was handled in earlier issues. I’ll continue to dig into the internal error issue next week. Thanks.

0reactions

SleeplessBytecommented, Nov 4, 2019

With 7.2.3 you should no longer need the flag – but warnings will show. Don’t be warned tho, they were already there… just not showing.

Top Results From Across the Web

[Bug] react-static build hangs forever on all templates #1298

The site is built into the dist directory. Observed Behavior. The process hangs forever on the "Bundling App..." step: lucien /c/projects/ ...

'npm start' is stuck on 'Starting the development server ...' after ...

And following the tutorials, the first thing I do is create a react app using 'create-react-app'. Though, it gave me a few high-severity ......

Error Boundaries - React

A class component becomes an error boundary if it defines either (or both) of the lifecycle methods static getDerivedStateFromError() or componentDidCatch() .

How to fix the Whitescreen After a Static Deployment with ...

In my case, I put them into a sub-directory react-app, ... app it's base URL, run npm run build again and copy the...

How I solved and debugged my Webpack issue through trial ...

When webpack bundles your source code, it can become difficult to track down errors and warnings to their original location.