Repository navigation
Conversation
Mirrors PlanoutApp/Planout-web#335. Dependencies - Expo SDK 58 beta (58.0.0-preview.3), React Native 0.88.0-rc.0, expo-router 58 - reanimated 4.7 / worklets 0.13, gesture-handler 3.3, screens 4.27, safe-area-context 5.9 - React 19.1.4 -> 19.3.0 in the `react19` catalog: RN 0.88 peers on ^19.2.3. The Next.js and TanStack Start apps share that catalog and both still typecheck and lint. - `@legendapp/list` 2 -> 3, which drops the root export; the list now imports from `@legendapp/list/react-native`. - `expo-network` is not added here: `@better-auth/expo` 1.4.0-beta.9 does not reach for it the way later versions do. Styling: NativeWind/react-native-css -> Uniwind Uniwind compiles Tailwind itself, so the PostCSS step and the `lightningcss` override (added only for react-native-css) are both gone. - metro wraps with `withUniwindConfig` - Uniwind resolves `@variant light` / `@variant dark` at runtime and requires both to declare the same variables. The web entries define `light:` as a class-only variant and take their light values from a plain `:root`, so the shared `theme.css` cannot be reshaped without breaking web light mode. `theme-native.css` holds the same tokens in the shape Uniwind needs, and apps/expo imports that instead. - dark mode follows the system scheme now; there is no `.dark` class to toggle - `uniwind-types.d.ts` is regenerated on every Metro run, so it is left as Uniwind writes it via a new `.prettierignore` Build config - `metro.config.js` -> `metro.config.ts`, which is typechecked (the `.js` never was, since the project sets `checkJs: false`). `metro-cache` was imported but is not a dependency; it now comes from `@expo/metro/metro-cache`. - app.config.ts drops `newArchEnabled`, `android.edgeToEdgeEnabled` and `reactCanary`, all of which SDK 58 no longer accepts - eas.json raises the eas-cli floor to 24.7.0 and matches the repo's Node/pnpm Verified: typecheck, lint and sherif pass across the workspace, and an Android Metro bundle exports cleanly. iOS was not bundled -- this was done on Windows. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- add nx.json with package-json target inference and ^build ordering - rewrite root scripts/deps to Nx, remove turbo tooling and Next/TanStack apps - strip turbo plugin from @acme/eslint-config, prune nextjs export - rework pnpm catalog: elysia/eden, MikroORM 7 + kysely, solid/vite-plus; align better-auth 1.7 and zod 4.5 - drop dead postcss wiring from @acme/tailwind-config
Land specs 02-08: MikroORM/Kysely + node:sqlite DB, better-auth, Elysia/Eden API, server and Solid web apps, Expo Eden client, Docker images, and CI/env/tooling cleanup (Bun setup, Nx-only workflow, SQLite env contract, no Turbo or dotenv-cli).
- return wrap(entity).toObject() from post detail/create/delete instead of MikroORM entities, which Elysia rendered as [object Object] - run better-auth migrations before betterAuth() so its schema check no longer logs a first-boot mismatch; initAuth is now async - await initAuth in the server entry - drop dead .turbo dockerignore entry and turbo.t3.gg comment
- declare env contracts in .env.schema files (shared root schema + per-app picks) - encrypt secrets at rest in gitignored .env.local via device-tied key; drop .env.example - typed ENV access replaces @t3-oss/env-core + zod env modules (server, web, expo) - Elysia server gets log redaction and leak prevention via varlock/auto-load - Docker server boots from deploy-key-encrypted .varlock-frozen-env (DATABASE_URL stays boot-supplied) - CI: add env schema validation job, drop the cp .env.example .env steps
|
@serbarla is attempting to deploy a commit to the t3-oss Team on Vercel. A member of the Team first needs to authorize it. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.