https://github.com/stephencweiss/onething/blob/9987276f76b1fd767edea0ff43337d6fe6335541/server/server.js#L38

We'll want to start putting variables that might be re-usable, such as URL, in the environment (i.e. so you can access as process.env.URL or something to that effect.

Or better yet, if you can get the hostname out of the react-app framework (like here), then you don't need to create an environment variable.

https://github.com/stephencweiss/onething/blob/master/server/server.js#L22-L24

Cool stuff! Something as monumental as an endpoint deserves a comment before. It would be helpful to detail things like: Description, Method (POST, GET, etc), Authentication (if any), Parameters (if any)

Next steps to consider looking into:

• Move the json array in the response to its own variable, like:

var response = [{id: 1, name: 'ab'}, {id: 2,name: 'def'}];
app.get('/api/users', (req, res) => {
  return res.status(200).json(response)
})

• Or better yet, move the logic for building the response object into its own file. That way, we can separate the mechanism for creating endpoints from the purpose that the end http endpoint executes. It will also be easier to organize down the road, if you need to include large database queries in the response logic.

https://github.com/stephencweiss/onething/blob/master/client/src/App.tsx#L27
Not a must, but adding a unique id per <p> might be helpful for identifying/styling records in the front-end in the future.

Local mail development:
https://mailtrap.io/faq
https://blog.mailtrap.io/sending-emails-with-nodemailer/#Installation