Error on npm start

[gordyd]

Error on npm start

[ryanyogan]

  match({ routes, location: req.url }, (error, redirectLocation, renderProps) => {
    if (error) {
      console.log('Error', error);
      res.status(500).send(error);
    } else if (redirectLocation) {
      res.redirect(302, redirectLocation.pathname + redirectLocation.search);
    } else if (renderProps) {
      const devTools = (isDev) ? <DevTools /> : null;
      const html = renderToString(
        <RouterContext {...renderProps} />
      );
      res.render('index', { isProd: (!isDev), html: html });
    } else {
      res.status(404).send('Not Found');
    }
  });

@GordyD It looks like it is just an issue of keeping up with react-router's fast moving changes. This is a bit more idiomatic.

[tzarger]

@GordyD If I removed {devTools} in app.js or rather set it to null ... the error goes away. Is this normal behavior on initial loading, etc.?

[robotate]

I get this error when i make requests to port 3000, but not 3001. The docs say to use :3001 for the dev server.

[GordyD]

Can you log the the req.url that this error was triggered on? This should help track what the issue is.

[tzarger]

@GordyD --- > @robotate is correct, I have localhost:3000 in cache, so that it before I could hit :3001 ... and if I do port 3001, no error, but port :3000 the app sort of shows and just throws that error in the console. So with that, I will close this as it was not an issue with the code itself; user, or cache, error.

[endigo]

How to fix it?
I think it's not cache error. RouterContext should have history prop. But history prop is just
{ }

[tzarger]

@endigo What I meant by cache, you know how when typing a URL I typed localhost:3 and hit tab and :3000 was in the URL cache so I saw the error. if I explicitly type localhost:3001 I didn't see the error. Are you seeing the error even when only hitting localhost:3001?

[endigo]

@tzarger No error occurs on port 3001. Only on port 3000. I was use firefox, chrome, chrome incognito mode, it's occurs same error

[snobear]

Yeah I get the same when hitting http://localhost:3001, and it seems benign. It seems to happen when first loading the site in the browser after an npm start. I cleared my cache in Chrome but it still happens. I'll try to nail it down and provide more info.

[GordyD]

Thanks for looking into this. If I get time to look over the weekend I'll try to investigate too.

[ReganHe]

@ryanyogan is correct.the 'renderProp' is not always has value.when it doesn't, the error reappears.