react-snap exits with status code 1 but no reason why about react-snap HOT 3 CLOSED

This is what I get

yarn build
...
yarn build-2-TODO
...
🕸  (1/4) /
🔥  /insights/ pageerror: Error: SyntaxError: Unexpected token < in JSON at position 0
    at http://localhost:45678/static/js/0.81dd690f.chunk.js:1:3016
    at call (../static/js/0.81dd690f.chunk.js:61:22)
    at step (../static/js/0.81dd690f.chunk.js:42:52)
    at call (../static/js/0.81dd690f.chunk.js:46:96)
    at step (../static/js/0.81dd690f.chunk.js:42:52)
    at next (../static/js/0.81dd690f.chunk.js:33:57)
    at <anonymous>
...

Which comes from

return fetch(`/api/get-stat/?id=${encodeURIComponent(m)}`

There is no such endpoint in static server used by reactSnap.

PS also call stack doesn't look helpful. TODO: report bug to create-react-app-typescript

UPD more precise error position based on SourceMaps at json pages/InsightsPage.tsx:58:32

from react-snap.

@stereobooster thanks for your help. Interestingly I still cannot reproduce getting a stack trace out of this myself. Maybe it's my version of node compared to yours:

$ npm --version
5.5.1
$ node --version
v9.0.0

Either way, I appreciate your help and I'll look into it from my end to figure out how to make sure that the app doesn't crash when trying to crawl when that API call is being made.

Edit: also instead of throwing errors when the fetch call fails, I just changed it to console.error for now and that fixes the exit status 1 code.

from react-snap.

I still cannot reproduce getting a stack trace out of this myself

yes this is mystery. My versions

node -v
v8.6.0
npm -v
5.3.0
yarn -v
1.2.1

You can detect reactSnap like this const snap = navigator.userAgent !== 'ReactSnap';. And use something else instead of actual content, for example react-content-loader

from react-snap.