bfollington

import React, { useReducer } from "react";
import { messages, initialMessagesState } from "./slices/messages";

const App: React.FC = () => {
  const [messageList, dispatch] = useReducer(
    messages.reducer,
    initialMessagesState
  );

  return (

screeny05

declare global {
    enum ChooseFileSystemEntriesType {
        'open-file',
        'save-file',
        'open-directory'
    }

    interface ChooseFileSystemEntriesOptionsAccepts {
        description?: string;
        mimeTypes?: string;

tannerlinsley

Replacing Create React App with the Next.js CLI

How dare you make a jab at Create React App!?

Firstly, Create React App is good. But it's a very rigid CLI, primarily designed for projects that require very little to no configuration. This makes it great for beginners and simple projects but unfortunately, this means that it's pretty non-extensible. Despite the involvement from big names and a ton of great devs, it has left me wanting a much better developer experience with a lot more polish when it comes to hot reloading, babel configuration, webpack configuration, etc. It's definitely simple and good, but not amazing.

Now, compare that experience to Next.js which for starters has a much larger team behind it provided by a world-class company (Vercel) who are all financially dedicated to making it the best DX you could imagine to build any React application. Next.js is the 💣-diggity. It has amazing docs, great support, can grow with your requirements into SSR or static site generation, etc.

So why

kyleshevlin

// Sometimes you'll have a component that you want to allow the consumer
// to render a different HTML element for semantic purposes. Use an `as`
// prop and a facade pattern to make it happen.

export function CallToAction({as = 'button', ...props}) {
  return <CallToActionFacade as={as} {...props} />
}

function CallToActionFacade({ as, ...props }) {
  switch (as) {

kyleshevlin

// One of my new favorite React Hook patternms is to create handler
// functions for a custom hook using `React.useMemo` instead of
// `React.useCallback`, like so:

function useBool(initialState = false) {
  const [state, setState] = React.useState(initialState)
  
  // Instead of individual React.useCallbacks gathered into an object
  // Let's memoize the whole object. Then, we can destructure the
  // methods we need in our consuming component.