Do you ever watch your view count rise and wonder which posts are being read the most? I know I did.
That is one reason why I chose to develop my own Dev.to analytics dashboard to display historical data such as view, reaction and follower increase over the last 24 hours, 7 days and 30 days.
Ever wondered if you can share interfaces, types and functions between TypeScript projects?
I’m currently developing a project consisting of two separate TypeScript applications, one being a React.js dashboard and the other an Azure Function app written in Node.js. As part of the project, the dashboard calls an API in the Azure Function app. This got me thinking, as I’m in control of both the data source and the application that uses the data, is there a way that I can share certain interfaces between the two projects?
When building an application powered by Next.js it’s probable that you’ll need to fetch data from either a file, an internal API route or an external API such as the Dev.to API. Moreover, determining what data fetching method to use in a Next.js application can easily become confusing — especially as it isn’t as simple as making an API request inside your components render function, as you might in a stock React app.
The following guide will help you carefully select the server-side data fetching method that suits your app (FYI you can use multiple methods in a single app)…
The final weekend of January 2021 was uneventful in comparison with other years — in the UK we were in full lockdown due to the Coronavirus. It was, however, the perfect opportunity to completely rewrite my personal website.
I decided to redesign and rewrite my website for several reasons:
Recently I’ve been using Next.js both at work and on after-work projects. Next.js is React framework that enables functionality such as server-side rendering and generating static websites. It has become my go-to technology when I’m building a frontend application, overtaking plain old React.
With Next.js you get many things out of the box such as built-in routing, automatic code splitting and it will even decide whether your app can be statically rendered or needs to be rendered server-side on every request — all of this without any configuration. …
The OpenAPI Initiative, previously known as the Swagger Specification, is a machine readable specification to describe RESTful web services such as an API. It’s used by many to describe what API queries an application can handle and when combined with the use of tools such as Swagger UI can make even the most complex APIs easy for developers to understand.
Using an OpenAPI Specification in your project should make it more understandable and easier for new developers to consume it. It is, however, easy for it to become outdated when changes are made to the functionality of the application, an…
IBMer, University of Portsmouth Alumni. Winchester based.