Update client and chat dependencies
What does this MR do?
- Updates the chat and client dependencies
- Adds a yarn.lock file for the chat -- why wasn't here one in the first place?
- Adds an info to the usages of request which was deprecated and should be replaced.
- Replaces the Debian Stretch node image in the docker-compose files with the Alpine ones, which are already used at some other places. That may reduce the build time, since the Alpine image is used anyway and has around 39 megabytes instead of 345 megabytes.
How confident are you it won't break things if deployed?
Seem to work. I get a "(blocked:scp)" info for requests to "info?t=" but that happens in the master as well. This is due to a misconfiguration because my service started on 18090 instead of 18080 and this points to the wrong port. Please check that out.
Links to related issues
How to test
Steps a reviewer can take to verify that this MR does what it says it does e.g.
- Checkout branch locally
- Login, browse through the page, check if you notice anything different.
Screenshots (if applicable)
Any relevant screenshots if this is a design / frontend change
Checklist
-
added a test, or explain why one is not needed/possible... -
no unrelated changes -
asked someone for a code review -
joined #foodsharing-beta channel at https://slackin.yunity.org -
added an entry to CHANGELOG.md (description, merge request link, username(s)) -
Once your MR has been merged, you are responsible to update the #foodsharing-beta Slack channel about what has been changed here. They will test your work in different browsers, roles or other settings