Goodbye Gatsby, Hello Next
Another year, another overhaul. This time I'm moving to Next.js and a controversial CSS framework. Starting with a fairly well built template, this is the story of how I moved from Gatsby to Next.js
Next.js: The Good, Bad and Ugly
Next.js is a framework for SSG SSR apps. But it is not all sunshine and rainbows. I've been building applications using Next.js for a couple of months now and this article is the summation of my struggles and *aha!* moments when using Next.js.
console.log the cool way
console.log is in every Developer's toolkit. But there's more to it than just the regular log method
Quick intro to bookmarklets and how to create one for life hacks
🐶 Automate linting with HuskyHusky
Using Husky for a git hook to format code on commit and before push
Dealing with async-await hell to write simpler and easy to understand code
🔎 Syntax Error: Expected Name, found <EOF>Gatsby
Solving an error without Googling it first is kind of not time saving.
🧲 Using Context with a HoCReact
How to use Context Provider to avoid props drilling? Bonus, cleaning up multi-context tree hell using a Higher order Component.
Is switch statement good? Is there something better out there?
🔥 Efficient workflow with ESLint and PrettierCode formatting
How I configure ESLint and Prettier to catch style and code issues early on
📥 Sharing state in GatsbyGatsby
Exploring how to create a shared state management system in GatsbyJS using Context Provider API
🌐 Holy Grail layouts in GatsbyGatsby
Exploring how to create a shared layout system in GatsbyJS
extracting reusable logic to a custom hook
match and matchAll can be used to match string using regex. But are they same?
🍪 Setting Cookies in Next.jsNext.js
Snippet showing how to set cookies for a given url in Next.js
A snippet showing how to override css-loader options in Next.js