I write all my newsletters using Kit β, my favorite newsletter platform.
Subscribe to the newsletter
Get the latest updates delivered directly to your inbox.
I write all my newsletters using Kit β, my favorite newsletter platform.
Get the latest updates delivered directly to your inbox.
Hey friend,
π¨ Before we start, I wanted to let you know that moving forward, this newsletter will be sent once every 3 weeks instead of weekly.
The main reason is that I've been working on a very exciting project π and most of my time will be invested in that.
I've been focusing on Shipping a course on transitioning developers transition into Engineering Managers π.
If you are interested, click this button and add yourself to the waitlist.
Add me to the Waitlist. |
You'll hear course updates, behind the scenes and can help craft the course curriculum
Moving on, another popular requested topic is Next.js 13 and how we can fetch data. Y'all really love Next.js 13, and here is a snippet.
With Next.js 13's experimental changes, how we fetch data will change significantly. Today's snippet shows you how you can fetch data statically in Next.js 13. In Next.js 12, we can bring data using getStaticProps if you can pre-build the page and your page is entirely static.
But with Next.js 13, we no longer need to use `getStaticProps` to fetch data statically. Instead, we can directly do that using `fetch.`
Fetch API now takes a property called { cache: 'no store' } as a 2nd parameter to the fetch function, allowing you to do this.
In the above snippet, we are fetching data from the Pokemon API, and since `fetch` returns a promise, we are calling `await` so we can wait for the promise to resolve. You don't need to provide this property explicitly, as it's there by default for us.
Wow, so many new folks have joined, Welcome!! π
This newsletter has grown quite a bit since I started it a few months ago. Iβd love to get to know you a bit better. Can you please click one of the links below to best describe your situation,
I hope you have a great day!