nandorojo

import * as schema from './schema' // make this point to your schema file
import { PgEnum, PgTableWithColumns } from 'drizzle-orm/pg-core'
import { createInsertSchema, createSelectSchema } from 'drizzle-zod'
import { z } from 'zod'

type ExtractPgTableKeys<T> = {
  [K in keyof T]: T[K] extends PgTableWithColumns<any> ? K : never
}[keyof T]

export const selects = Object.fromEntries(

nandorojo

You just got this error after running npx expo run:ios or building React Native locally:

Error: xcrun simctl boot 62F02616-B3DF-4F78-9770-74AD88CB7DC2 exited with non-zero code: 60
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=60):
Unable to boot the Simulator.
launchd failed to respond.
Underlying error (domain=com.apple.SimLaunchHostService.RequestError, code=4):
        Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding

nandorojo

If you get this error running npx expo run:ios:

Error: xcrun simctl boot 62F02616-B3DF-4F78-9770-74AD88CB7DC2 exited with non-zero code: 60
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=60):
Unable to boot the Simulator.
launchd failed to respond.
Underlying error (domain=com.apple.SimLaunchHostService.RequestError, code=4):
        Failed to start launchd_sim: could not bind to session, launchd_sim may have crashed or quit responding
Error: xcrun simctl boot 62F02616-B3DF-4F78-9770-74AD88CB7DC2 exited with non-zero code: 60

nandorojo

import { createContext as create, useContext } from 'react'

export function createContext<T>(initial?: T) {
  const ctx = create<T>(initial ?? (null as any))

  return Object.assign(
    function Provider(props: React.ComponentProps<typeof ctx.Provider>) {
      return <ctx.Provider {...props} />
    },
    ctx,

nandorojo

// this won't ever get imported on native, but we put this file here to make that clear
export default ({children}) => children

nandorojo

When I built my first React Native app, I had some prior web experience. Using React on iOS and Android felt like a natural way to apply my skills.

But I was suprised to learn, the hard way, that my web-developer-way-of-thinking didn't apply to native apps.

To understand why, let's start with the navigation layout. Each website has unique page primitives. The header at the top of the page, the sidebar menu, the footers – they're all hand-rolled.

You write a <header> and all you get is an empty box. You then use your own JavaScript and CSS to make it useful.

The way these elements look and feel is part of your brand. If your header looks just like another website, something feels off.

nandorojo

import {
  MaskOptions,
  addChildren,
  applyMask,
  createStrengthenMask,
  createTheme,
  createWeakenMask,
} from '@tamagui/create-theme'
import { mauve, slate, mauveDark, slateDark } from '@tamagui/colors'

nandorojo

Add the package name you want to your package.json dependencies, and then make the value npm:<actual-package-name>. You can also add a version to the end.

package.json

{
  "dependencies": {
    "moti18": "npm:moti@0.18.0"
  }
}

nandorojo

First, copy the config plugin from this repo: https://github.com/gaishimo/eas-widget-example

You can reference my PRs there too (which, at the time of writing, aren't merged).

After adding the config plugin (see app.json) with your dev team ID, as well as a bundle ID, you can edit the widget folder to edit your code. Then npx expo run:ios (or npx expo run:android).

Workflow

After npx expo run:ios, open the ios folder, and open the file that ends in .xcworkspace in XCode. Make sure you have the latest macOS and XCode versions. If you don't, everything will break.

nandorojo

import {
  FormProvider,
  useForm,
  useWatch,
  useFormState,
  useFormContext,
  Path,
  ControllerProps,
  Controller,
  UseFormProps,