2021-03-25
4515
#node
Geshan Manandhar
39801
Mar 25, 2021 ⋅ 16 min read

How to send emails with Node.js using SendGrid

Geshan Manandhar Geshan is a seasoned software engineer with more than a decade of software engineering experience. He has a keen interest in REST architecture, microservices, and cloud computing. He also blogs at geshan.com.np.

Recent posts:

How to speed up long lists with TanStack Virtual

How to speed up long lists with TanStack Virtual

Build fast, scalable UIs with TanStack Virtual: virtualize long lists, support dynamic row heights, and implement infinite scrolling with React.

Ikeh Akinyemi
Nov 28, 2025 ⋅ 8 min read
why you should ci cd your project from day one

Why you should set up CI/CD from day one for your apps

CI/CD isn’t optional anymore. Discover how automated builds and deployments prevent costly mistakes, speed up releases, and keep your software stable.

Lewis Cianci
Nov 28, 2025 ⋅ 9 min read

Top 5 AI code review tools in 2025

A quick comparison of five AI code review tools tested on the same codebase to see which ones truly catch bugs and surface real issues.

Emmanuel John
Nov 27, 2025 ⋅ 7 min read
css corner shape property

How to create fancy corners using CSS corner-shape

Learn about CSS’s corner-shape property and how to use it, as well as the more advanced side of border-radius and why it’s crucial to using corner-shape effectively.

Daniel Schwarz
Nov 26, 2025 ⋅ 7 min read
View all posts

2 Replies to "How to send emails with Node.js using SendGrid"

  1. Hi there! Really good artcle! Just one minor thing mate, when you are creating the Express application and defining the port, I think you should be first grabbing what it comes from the environment variable and then user port 3000 as fallback, so something like: const port = process.env.PORT || 3000; as you did for example with the statusCode.

  2. Hey, great article! Just a small suggestion, when setting up the Express application and specifying the port, it might be beneficial to prioritize fetching the port value from the environment variable first, and then fallback to using port 3000 if it’s not available.
    Thank you.

Leave a Reply

Would you be interested in joining LogRocket's developer community?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now