Errata

Full Stack Serverless

Errata for Full Stack Serverless

Submit your own errata for this product.

The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.

Color Key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted by Date Submitted
Chapters 4 & 5
Code samples - Router.js, Profile.js

Listed as 'minor technical' because this is probably because the libraries have evolved since publication however the code from both online and github repo seem to need updating. This is for Chapters 4 and 5.

- Router.js : Switch needs to be changed to Routes (and I think component -> element)
- AmplifySignOut has, I think, changed (per authors github)
- Authenticator v2 has seemingly quite a different syntax now (per amplify docs)

In authors github repo
- Authors git repo has a typo in Nav.js : '>>Profile' should be '>Profile'
- Profile.js has 'aws-amplify-react' but think should be '@aws-amplify/ui-react'

Alex C  Nov 11, 2022 
Chapter 6
Adding the Custom Logic for Resizing the Image

Installing the sharp image library doesn't work. The probelm is that the version is now too old to install without the target flag (which was used earlier as I see in errata). According to the comment that I linked the version should be v0.25.0+. But right now it's 0.23.2. I fixed this by changing it to 0.25.4 and the amplify push worked.

https://github.com/lovell/sharp/issues/2128#issuecomment-600232917

Teemu Helenius  Jan 16, 2021 
Chapter 4 & 5
Protected Component & Creating the protectedRoute Hook

There's a problem with the protected route. The authorization is done in the useEffect hook so it applies after the page is rendered. So the user can slow down the internet connection etc. and see the content on the protected page for a short time before redirecting. So it isn't actually protected.

Teemu Helenius  Jan 16, 2021