Closed MFry closed 7 years ago
I have same issue with v0.2.0 but it is ok with v0.1.4. (node v6.11.0, npm v5.2.0)
I am having the same issue with v0.2.0.
Same issue here with v0.2.0. Would love to have this resolved so I can plug and play with heroku + create-react-app build pack. This currently stalls the build indefinitely.
Update: this works for me https://github.com/gr33k01/custom-react-scripts/commit/f6e1e4fd8dad2b3484e948288cba72fbb1ff8a5e
I'm facing this problem too. As a workaround I followed the steps:
timeout-cli
and shelljs
packages as dev dependenciesnode build.js
build.js
file with the content below:
const shell = require('shelljs')
const successMessage = 'The build folder is ready to be deployed.' const result = shell.exec('timeout react-scripts build -t 1m')
if (result.stdout.includes(successMessage)) process.exit(0) else process.exit(result.code)
This is definitely **not a good solution**, but it doesn't hide any build issues and it makes sure the build script finally ends on its own.
I can finally deploy to Netlify now.
The solution specified by @gr33k01 seems promising, but I haven't tested it yet.
PR is merged now, sorry for the delay
It's merged but npm package is not updated :(
Hey @hipertracker, new version is published now. Let me know if it's fine!
@kitze I've just tested. The new release worked fine 👍 Thanks, guys!
Works fine now. Thanks!
Is this a bug report?
Yes
Can you also reproduce the problem with npm 4.x?
Environment
node -v
:v7.10.1
npm -v
:5.3.0
and4.6.1
yarn --version
(if you use Yarn):0.27.5
npm ls react-scripts
(if you haven’t ejected):Steps to Reproduce
Expected Behavior
It terminates in some finite amount of time.
(Write what you thought would happen.)
Actual Behavior
The files are built but the built halts at the point:
It awaits for some input as the carat is there.
This was reproduced on my mac, windows and on Travis CI. I have also had it running on my machine, to make sure it just didn't take a very long time, but it has been running for over two hour and still hasn't stopped.
Interestingly, if you attempt to terminate the batch script
Entering either Y or N will result in the script terminating.
Reproducible Demo