I recently finished a really big refactoring from NextJS 13 to NextJS 14, mostly prompted by the server actions stuff, allowing me to entirely drop a publicly exposed GraphQL service, and do everything in backend Postgres. That all worked wonderfully. Very pleased with that – any time I can delete stuff and yet maintain the … Read more
I recently had to do a proof of concept site using NextJS 14. I hadn’t used NextJS since version 11, and who knew how much could change in 3 major versions? The big change is the use of Server Actions, and then the App Router / /app directory, as opposed to the older client server … Read more
Of all the hooks available in React, useReducer is easily my favourite. It’s nice to be able to solve simple problems with useState, but in component’s with even a smaller amount of complexity than can be solved with a boolean state value, I tend to favour useReducer. Let’s dig in, see some examples, and find … Read more
In this post I will show you a way to create a unit tested React component that allows you to pass either a plain string, or one or more <p>text goes here</p> tags, and then render out only the first X words. When the word limit is hit, a ‘Show More’ button will display, and … Read more
Today’s error is likely going to make you want to kick yourself. I certainly felt like quite a wally after realising my mistake. But I do like to blog these as I hope that by doing so, I shame myself into remembering the solution in the future. OK, the error message: It doesn’t massively impact … Read more
You may well have come across the warning in React where you are rendering out a list of things, and you forget to give each element a unique key. If you do that, you get the following showing your browser’s console: Warning: Each child in a list should have a unique “key” prop. In this … Read more
