Update dependencies

[nikdo]

• [x] update to latest react
  • [x] check React changelog
• [x] update client dependencies
• [x] find out why nothing is diplayed on spot detail
• [x] test everything
  • [x] autosuggest
  • [x] search icon transition
  • [x] routing
  • [x] route transition
  • [x] routing history
  • [x] chart ticks alignment (see d3AxisOffset in constants)
• [x] update devDependencies
  • [x] fix storybook
  • [x] migrate storybook config
  • [x] fix font in storybook
• [x] update API dependencies
  • [x] find out how to test cache
  • [x] upgrade make-fetch-happen
  • [x] verify that caching works
  • [x] test everything
• [x] publish
• [x] test chart scrolling and tooltip on mobile device
• [ ] move cacache question to the new cacache repository location

[nikdo]

Caching takeaways

Express res.json sends a 304 status code if the response hasn't changed. So querying spot detail on our API returns 304 if DarkSky returns the same response. DarkSky returns the same response only if it is cached because otherwise, it returns new data with each request.

This means that if 304 is logged as status code by express, the forecast is cached.

[nikdo]

Time estimated: 3h Time spent: 11h

Why:

• API caching verification after make-fetch-happen upgrade
• fixing broken storybook
• fixing linter issues after standard upgrade
• investigating problem caused by history package bug