@meith/web 0.16.0

package/app/twitter-image.ts

@@ -0,0 +1,11 @@
+import { renderBrandSocial } from '@/server/brand-mark'
+
+export const dynamic = 'force-dynamic'
+
+export const size = { width: 1200, height: 630 }
+
+export const contentType = 'image/png'
+
+export default function TwitterImage(): Promise<Response> {
+  return renderBrandSocial()
+}

package/app/viewforum.php/page.tsx

@@ -0,0 +1,11 @@
+import { serveLegacyUrl } from '@/server/legacy-redirect'
+
+export const dynamic = 'force-dynamic'
+
+export default async function ViewforumPage({
+  searchParams,
+}: {
+  searchParams: Promise<Record<string, string | string[] | undefined>>
+}): Promise<never> {
+  return serveLegacyUrl('viewforum.php', await searchParams)
+}

package/app/viewtopic.php/page.tsx

@@ -0,0 +1,11 @@
+import { serveLegacyUrl } from '@/server/legacy-redirect'
+
+export const dynamic = 'force-dynamic'
+
+export default async function ViewtopicPage({
+  searchParams,
+}: {
+  searchParams: Promise<Record<string, string | string[] | undefined>>
+}): Promise<never> {
+  return serveLegacyUrl('viewtopic.php', await searchParams)
+}

package/bin/forum-web.mjs

@@ -0,0 +1,241 @@
+#!/usr/bin/env node
+/**
+ * `forum-web` — the bin that makes `@meith/web` runnable as a plain
+ * dependency of an external board workspace (see docs/development.md,
+ * "Consuming the board from a workspace").
+ *
+ * A Next.js app is not consumable as a bare dependency: `next dev|build|start`
+ * need to run with the app's own directory as the project root, and the
+ * board-config seam (`@board/config` / `@board/plugins`, see
+ * docs/architecture.md) is a pair of tsconfig path aliases that inside this
+ * monorepo point at `apps/community`'s own files. Neither survives npm
+ * installing this package into somebody else's workspace unchanged.
+ *
+ * So on every invocation this bin:
+ *
+ *   1. Copies this package's own Next app sources into `.meith/app/` inside
+ *      the invoking workspace (the current working directory) — gitignored,
+ *      regenerated every time, never a merge target.
+ *   2. Writes `.meith/app/tsconfig.json`, a fresh tsconfig whose `paths`
+ *      point `@board/config` and `@board/plugins` at *this workspace's own*
+ *      `community.config.ts` / `community.plugins.ts` — the same seam, wired
+ *      to a different pair of files. tsconfig `paths` are a compiler/bundler
+ *      alias, not a package boundary, so nothing stops one from naming a
+ *      path two directories up; that is the whole trick.
+ *   3. Runs `next dev|build|start` with `.meith/app/` as the project root.
+ *
+ * `.meith/app/` sits exactly two directories below the workspace root
+ * (`<root>/.meith/app`) on purpose: `next.config.mjs` (copied verbatim, see
+ * below) computes its own workspace root as two directories up from itself,
+ * so materializing at that exact depth keeps that computation correct
+ * without touching the file.
+ *
+ * This assumes a *hoisted* `node_modules` (npm, yarn classic, or pnpm with
+ * `node-linker=hoisted`) — see docs/development.md for why.
+ *
+ * `boards/stock` (docker/Dockerfile) is this bin's one *in-repo* consumer,
+ * and it has neither a hoisted `node_modules` nor a two-directories-up
+ * workspace root — it is a workspace member of this monorepo's own
+ * (non-hoisted) pnpm install, nested two directories deeper again. Two
+ * environment variables, set only by that workspace's own `build`/`dev`
+ * scripts, cover the difference without changing anything for a real
+ * external board, which never sets either: `FORUM_WORKSPACE_ROOT`
+ * (apps/community/next.config.mjs) points tracing at this repository's real
+ * root, and `FORUM_ALIASES_FROM` (`monorepoAliases()` below) carries this
+ * repository's own `@meith/*` tsconfig aliases into the generated tsconfig,
+ * since packages here resolve each other through those aliases rather than
+ * through real `dependencies` entries a hoisted `node_modules` would need.
+ */
+import { spawn } from 'node:child_process'
+import { cpSync, existsSync, mkdirSync, readFileSync, rmSync, writeFileSync } from 'node:fs'
+import { createRequire } from 'node:module'
+import { dirname, join, relative, resolve, sep } from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const here = dirname(fileURLToPath(import.meta.url))
+const packageRoot = join(here, '..')
+const workspaceRoot = process.cwd()
+const appDir = join(workspaceRoot, '.meith', 'app')
+
+// `next dev|build` runs with `.meith/app` as its own cwd (see `run()` below),
+// so a relative FORUM_WORKSPACE_ROOT / FORUM_ALIASES_FROM — the shape
+// boards/stock/package.json's scripts write, relative to *this* process's
+// own cwd (the board's own directory) — would resolve against the wrong
+// directory if left for next.config.mjs to resolve itself. Rewriting them to
+// absolute paths here, before spawning, means both env vars mean the same
+// thing regardless of which process reads them.
+for (const name of ['FORUM_WORKSPACE_ROOT', 'FORUM_ALIASES_FROM']) {
+  if (process.env[name]) process.env[name] = resolve(workspaceRoot, process.env[name])
+}
+
+// Files this package ships (see its `files` allowlist) that belong inside
+// the materialized app. Board files (community.config.ts, board.plugins.json,
+// community.plugins.ts) are never copied — they are read in place, from the
+// workspace, through the generated tsconfig instead.
+const APP_ENTRIES = [
+  'app',
+  'src',
+  'next.config.mjs',
+  'postcss.config.mjs',
+  'components.json',
+  'instrumentation.ts',
+  'proxy.ts',
+]
+
+function fail(message) {
+  console.error(`forum-web: ${message}`)
+  process.exit(1)
+}
+
+function toPosixRelative(from, to) {
+  const rel = relative(from, to).split(sep).join('/')
+  return rel.startsWith('.') ? rel : `./${rel}`
+}
+
+/**
+ * A board outside this monorepo has a hoisted `node_modules` (see the module
+ * comment), so plain bare-specifier resolution reaches every `@meith/*`
+ * package this app's dependency graph needs, and `transpilePackages`
+ * (apps/community/next.config.mjs) is what lets Next compile the `.ts`
+ * source that resolution lands on. A board built *inside* this monorepo's
+ * own pnpm install has no such hoisting — packages here resolve each other
+ * through tsconfig path aliases straight to source (docs/architecture.md,
+ * "The board-config seam"; docs/development.md, "The workspace") rather than
+ * through real `dependencies` entries, so plain node_modules resolution
+ * finds nothing for most of them.
+ *
+ * `FORUM_ALIASES_FROM`, set only by docker/Dockerfile for `boards/stock`,
+ * names that other tsconfig (this repository's own `tsconfig.base.json`).
+ * When set, every `@meith/*` alias it declares is copied into the
+ * materialized app's own generated tsconfig, rebased to be relative to
+ * `.meith/app` — the same aliases apps/community's own tsconfig.json
+ * hand-maintains for exactly this reason. Unset (the default, and the only
+ * path a real external board ever takes), this is a no-op.
+ */
+function monorepoAliases() {
+  const configFile = process.env.FORUM_ALIASES_FROM
+  if (!configFile) return {}
+
+  const sourceDir = dirname(resolve(configFile))
+  const source = JSON.parse(readFileSync(configFile, 'utf8'))
+  const paths = source.compilerOptions?.paths ?? {}
+
+  const aliases = {}
+  for (const [alias, targets] of Object.entries(paths)) {
+    // `@board/config`/`@board/plugins` are this workspace's own seam, wired
+    // below to *this* board's files — never to whatever apps/community's own
+    // tsconfig happens to alias them to.
+    if (alias === '@board/config' || alias === '@board/plugins') continue
+    aliases[alias] = targets.map((target) => toPosixRelative(appDir, join(sourceDir, target)))
+  }
+  return aliases
+}
+
+function materialize() {
+  const boardConfig = join(workspaceRoot, 'community.config.ts')
+  const boardPlugins = join(workspaceRoot, 'community.plugins.ts')
+
+  if (!existsSync(boardConfig)) {
+    fail(
+      `no community.config.ts in ${workspaceRoot}. Run forum-web from a board's own ` +
+        'directory — the one create-meith scaffolded, or one shaped like it.',
+    )
+  }
+
+  // Replace each shipped entry, but never `rm -rf` the whole directory:
+  // `.next` lives here too once a build has run, and `forum-web start` needs
+  // that build still on disk after this same function re-materializes the
+  // sources ahead of launching the standalone server.
+  mkdirSync(appDir, { recursive: true })
+
+  for (const entry of APP_ENTRIES) {
+    const source = join(packageRoot, entry)
+    const target = join(appDir, entry)
+    rmSync(target, { recursive: true, force: true })
+    if (!existsSync(source)) continue
+    cpSync(source, target, { recursive: true })
+  }
+
+  const tsconfig = {
+    compilerOptions: {
+      target: 'ES2022',
+      lib: ['dom', 'dom.iterable', 'esnext'],
+      module: 'esnext',
+      moduleResolution: 'bundler',
+      jsx: 'preserve',
+      allowJs: false,
+      resolveJsonModule: true,
+      esModuleInterop: true,
+      isolatedModules: true,
+      skipLibCheck: true,
+      noEmit: true,
+      incremental: true,
+      strict: true,
+      plugins: [{ name: 'next' }],
+      paths: {
+        ...monorepoAliases(),
+        '@/*': ['./src/*'],
+        '@board/config': [toPosixRelative(appDir, boardConfig)],
+        '@board/plugins': [toPosixRelative(appDir, boardPlugins)],
+      },
+    },
+    include: ['next-env.d.ts', '**/*.ts', '**/*.tsx', '.next/types/**/*.ts'],
+    exclude: ['node_modules'],
+  }
+
+  writeFileSync(join(appDir, 'tsconfig.json'), `${JSON.stringify(tsconfig, null, 2)}\n`)
+
+  // next dev/build reads its own next-env.d.ts if present; an empty one is
+  // enough, and next regenerates it with the right content on first run.
+  writeFileSync(
+    join(appDir, 'next-env.d.ts'),
+    '/// <reference types="next" />\n/// <reference types="next/image-types/global" />\n',
+  )
+}
+
+function resolveNextBin() {
+  // Resolved from this package's own directory rather than the workspace
+  // root: `next` is @meith/web's dependency, not necessarily the workspace
+  // manifest's, and resolving from here finds it either way — hoisted to
+  // the workspace root (npm, yarn classic) or nested under this package's
+  // own node_modules (pnpm's default, non-hoisted layout).
+  const require = createRequire(join(packageRoot, 'package.json'))
+  try {
+    return require.resolve('next/dist/bin/next')
+  } catch {
+    fail("could not find next's own CLI from @meith/web — is next installed in this workspace?")
+  }
+}
+
+function run(executable, args, cwd) {
+  const child = spawn(executable, args, { cwd, stdio: 'inherit' })
+  child.on('exit', (code, signal) => process.exit(code ?? (signal ? 1 : 0)))
+  child.on('error', (error) => fail(error.message))
+}
+
+const [, , command, ...rest] = process.argv
+
+if (!['dev', 'build', 'start'].includes(command ?? '')) {
+  console.error('Usage: forum-web <dev|build|start> [next arguments]')
+  process.exit(1)
+}
+
+materialize()
+
+if (command === 'start') {
+  // `next.config.mjs` sets `output: 'standalone'`, and a standalone build is
+  // run from its own traced server.js, not `next start` (see docker/Dockerfile
+  // and docker/entrypoint.sh, which run the image's board the same way). The
+  // tracing root is the workspace root (see the module comment on why
+  // `.meith/app` sits exactly two levels below it), so the standalone bundle
+  // preserves that same relative path down to the app directory.
+  const standaloneRoot = join(appDir, '.next', 'standalone')
+  const serverScript = join(standaloneRoot, relative(workspaceRoot, appDir), 'server.js')
+  if (!existsSync(serverScript)) {
+    fail(`no standalone build at ${serverScript} — run "forum-web build" first.`)
+  }
+  run(process.execPath, [serverScript, ...rest], standaloneRoot)
+} else {
+  const nextBin = resolveNextBin()
+  run(process.execPath, [nextBin, command, ...rest], appDir)
+}

package/components.json

@@ -0,0 +1,21 @@
+{
+  "$schema": "https://ui.shadcn.com/schema.json",
+  "style": "base-nova",
+  "rsc": true,
+  "tsx": true,
+  "tailwind": {
+    "config": "",
+    "css": "app/globals.css",
+    "baseColor": "neutral",
+    "cssVariables": true,
+    "prefix": ""
+  },
+  "aliases": {
+    "components": "@/components",
+    "utils": "@/lib/utils",
+    "ui": "@/components/ui",
+    "lib": "@/lib",
+    "hooks": "@/hooks"
+  },
+  "iconLibrary": "lucide"
+}

package/instrumentation.ts

@@ -0,0 +1,18 @@
+export async function register(): Promise<void> {
+  // biome-ignore lint/style/noProcessEnv: build-time runtime token, not config; see above
+  if (process.env.NEXT_RUNTIME !== 'nodejs') return
+
+  const { assertRuntimeEnv, initTracing } = await import('@meith/core')
+
+  const env = assertRuntimeEnv()
+
+  if (env.DATA_SOURCE === 'fixture') {
+    // biome-ignore lint/suspicious/noConsole: pre-logger boot diagnostic
+    console.info(
+      '[forum] DATA_SOURCE=fixture — running against in-memory sample data. ' +
+        'Set DATABASE_URL to use Postgres.',
+    )
+  }
+
+  await initTracing('meith-web')
+}

package/next.config.mjs

@@ -0,0 +1,182 @@
+import { existsSync } from 'node:fs'
+import path from 'node:path'
+import { fileURLToPath } from 'node:url'
+
+const here = path.dirname(fileURLToPath(import.meta.url))
+
+// Two directories up from this file's own location — correct whenever this
+// file sits at that fixed depth below the real workspace root: in place at
+// `apps/community` inside this monorepo, or materialized to `.meith/app`
+// inside a *board whose own directory sits two levels below its own
+// `node_modules`* (a create-meith scaffold with hoisted node_modules, per
+// docs/development.md, "Consuming the board from a workspace").
+//
+// `boards/stock` (docker/Dockerfile) is neither: it is a workspace member of
+// *this* monorepo's own pnpm install, which does not hoist, so its real
+// dependencies (including `next` itself) resolve through this repository's
+// root `node_modules`, two directories further up again — a fixed offset
+// this file cannot compute from its own path alone, because pnpm resolves
+// its dependencies through symlinks into a central store rather than by
+// nesting a workspace member two directories below everything it needs.
+// FORUM_WORKSPACE_ROOT lets the Dockerfile say so explicitly, without
+// changing the default for every other consumer this computation already
+// serves correctly.
+const workspaceRoot = process.env.FORUM_WORKSPACE_ROOT
+  ? path.resolve(process.env.FORUM_WORKSPACE_ROOT)
+  : path.join(here, '../../')
+
+// How many `../` this file's own directory is below workspaceRoot — 2 by
+// construction in the default case (see above), more when
+// FORUM_WORKSPACE_ROOT points further up. Used below instead of a literal
+// `'../../'` wherever a *relative* climb has to reach the same root, because
+// `outputFileTracingIncludes` (unlike `outputFileTracingRoot` and
+// `turbopack.root`) resolves its globs relative to this directory itself,
+// not against `workspaceRoot` — an absolute glob there silently matches
+// nothing useful once it is rejoined onto this directory downstream.
+const upToWorkspaceRoot = path.relative(here, workspaceRoot).split(path.sep).join('/')
+
+const loadedEnvFiles = []
+for (const name of ['.env.local', '.env']) {
+  const file = path.join(workspaceRoot, name)
+  if (!existsSync(file)) continue
+  process.loadEnvFile(file)
+  loadedEnvFiles.push(name)
+}
+
+if (process.env.NODE_ENV !== 'production' && loadedEnvFiles.length > 0) {
+  console.log(`- Environments: ${loadedEnvFiles.join(', ')} (${workspaceRoot})`)
+}
+
+const nextConfig = {
+  output: 'standalone',
+  poweredByHeader: false,
+  distDir: process.env.FORUM_DIST_DIR ?? '.next',
+
+  serverExternalPackages: [
+    '@aws-sdk/client-s3',
+    '@aws-sdk/s3-request-presigner',
+    'postgres',
+    '@jsquash/jpeg',
+    '@jsquash/png',
+    '@jsquash/resize',
+    'nodemailer',
+  ],
+  outputFileTracingRoot: workspaceRoot,
+  // Turbopack infers a project root by walking up for a lockfile, and
+  // otherwise stops at this app's own directory — which for a materialized
+  // app (apps/community/bin/forum-web.mjs) is two directories below the
+  // real one. Left unset, Turbopack's own Node.js transform pool (postcss,
+  // for instance) cannot see the invoking workspace's node_modules at all,
+  // and fails with "Cannot find module" for a dependency that plain Node
+  // resolution finds without trouble.
+  turbopack: {
+    root: workspaceRoot,
+  },
+  // The output-file tracer only follows the CJS half of @swc/helpers' dual
+  // package and misses the `esm/` variant next's own require-hook resolves at
+  // runtime, so the standalone build ships a `@swc/helpers` directory missing
+  // its esm/ half. next resolves the package from its own nested pnpm store
+  // entry (node_modules/.pnpm/next@…/node_modules/@swc/helpers), which is a
+  // symlink into node_modules/.pnpm/@swc+helpers@0.5.23/node_modules/@swc/helpers
+  // — so that is the path that has to be complete, not the app's own copy.
+  outputFileTracingIncludes: {
+    '/**': [
+      `${upToWorkspaceRoot}/node_modules/.pnpm/@swc+helpers@0.5.23/node_modules/@swc/helpers/**/*`,
+    ],
+  },
+  images: {
+    unoptimized: true,
+  },
+  // Every `@meith/*` package this app's dependency graph reaches — not just
+  // the ones apps/community imports directly. All of them ship TypeScript
+  // source with no build step (see docs/release.md, "They ship TypeScript
+  // source, deliberately"), and inside this monorepo every one of them is
+  // resolved through a tsconfig path alias straight to its source file,
+  // bypassing node_modules — which is why this list used to be a small,
+  // seemingly arbitrary subset: only the packages some other resolution path
+  // happened to touch via node_modules ever needed it here.
+  //
+  // A materialized workspace's own generated tsconfig carries no such alias
+  // map (see apps/community/bin/forum-web.mjs) — only `@board/config` and
+  // `@board/plugins`, the seam itself. Every other `@meith/*` specifier
+  // resolves the ordinary way once this package is npm-installed, which
+  // means every one of them needs this same source-compilation treatment,
+  // or the build fails with "Unknown module type" on its `src/index.ts`.
+  // Computed by walking this app's own imports plus every `@meith/*`
+  // package's own "dependencies" transitively — see docs/development.md,
+  // "Consuming the board from a workspace".
+  transpilePackages: [
+    '@meith/accounts',
+    '@meith/admin',
+    '@meith/antispam',
+    '@meith/api',
+    '@meith/attachments',
+    '@meith/authorization',
+    '@meith/avatars',
+    '@meith/core',
+    '@meith/db',
+    '@meith/demo',
+    '@meith/drafts',
+    '@meith/drivers',
+    '@meith/events',
+    '@meith/forums',
+    '@meith/groups',
+    '@meith/i18n',
+    '@meith/import',
+    '@meith/install',
+    '@meith/mail',
+    '@meith/markdown',
+    '@meith/marketplace',
+    '@meith/messages',
+    '@meith/moderation',
+    '@meith/notifications',
+    '@meith/plugin-dues',
+    '@meith/plugin-kit',
+    '@meith/polls',
+    '@meith/posts',
+    '@meith/profile-fields',
+    '@meith/relations',
+    '@meith/reputation',
+    '@meith/runtime',
+    '@meith/search',
+    '@meith/settings',
+    '@meith/signatures',
+    '@meith/subscriptions',
+    '@meith/tasks',
+    '@meith/theme-clubhouse',
+    '@meith/theme-default',
+    '@meith/theme-kit',
+    '@meith/theme-midnight',
+    '@meith/theme-phasebook',
+    '@meith/theme-raidframe',
+    '@meith/threads',
+    '@meith/ui',
+    '@meith/upgrade',
+    // Only reached through the `@meith/web/config` subpath, and only from a
+    // materialized workspace's own community.config.ts — inside this
+    // monorepo apps/community never imports itself by package name. Real
+    // once npm resolves this package into another workspace's node_modules,
+    // so it needs the same source-compilation treatment as everything else
+    // in this list.
+    '@meith/web',
+  ],
+  async headers() {
+    return [
+      {
+        source: '/:path*',
+        headers: [
+          { key: 'X-Content-Type-Options', value: 'nosniff' },
+          { key: 'Referrer-Policy', value: 'strict-origin-when-cross-origin' },
+          { key: 'Strict-Transport-Security', value: 'max-age=63072000' },
+          { key: 'X-Frame-Options', value: 'SAMEORIGIN' },
+          {
+            key: 'Permissions-Policy',
+            value: 'camera=(), microphone=(), geolocation=()',
+          },
+        ],
+      },
+    ]
+  },
+}
+
+export default nextConfig

package/package.json

@@ -0,0 +1,99 @@
+{
+  "name": "@meith/web",
+  "version": "0.16.0",
+  "description": "The board itself: the Next.js app, and the forum-web bin that materializes it into an external board workspace.",
+  "license": "LGPL-3.0-or-later",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/meith-dev/meith.git",
+    "directory": "apps/community"
+  },
+  "bin": {
+    "forum-web": "./bin/forum-web.mjs"
+  },
+  "exports": {
+    "./config": "./src/config.ts"
+  },
+  "files": [
+    "bin",
+    "app",
+    "src",
+    "next.config.mjs",
+    "postcss.config.mjs",
+    "components.json",
+    "instrumentation.ts",
+    "proxy.ts",
+    "!src/**/*.test.*",
+    "!src/**/*.type-test.*",
+    "!app/**/*.test.*",
+    "!app/**/*.type-test.*"
+  ],
+  "publishConfig": {
+    "access": "public"
+  },
+  "dependencies": {
+    "@swc/helpers": "0.5.23",
+    "@tailwindcss/postcss": "^4.3.3",
+    "next": "16.3.1",
+    "postcss": "^8.5",
+    "react": "19.2.8",
+    "react-dom": "19.2.8",
+    "tailwindcss": "^4.3.3",
+    "typescript": "7.0.2",
+    "@types/react": "^19",
+    "@types/react-dom": "^19",
+    "@meith/accounts": "0.16.0",
+    "@meith/antispam": "0.16.0",
+    "@meith/authorization": "0.16.0",
+    "@meith/attachments": "0.16.0",
+    "@meith/api": "0.16.0",
+    "@meith/admin": "0.16.0",
+    "@meith/avatars": "0.16.0",
+    "@meith/db": "0.16.0",
+    "@meith/drivers": "0.16.0",
+    "@meith/events": "0.16.0",
+    "@meith/drafts": "0.16.0",
+    "@meith/forums": "0.16.0",
+    "@meith/groups": "0.16.0",
+    "@meith/core": "0.16.0",
+    "@meith/demo": "0.16.0",
+    "@meith/mail": "0.16.0",
+    "@meith/install": "0.16.0",
+    "@meith/import": "0.16.0",
+    "@meith/markdown": "0.16.0",
+    "@meith/marketplace": "0.16.0",
+    "@meith/moderation": "0.16.0",
+    "@meith/notifications": "0.16.0",
+    "@meith/profile-fields": "0.16.0",
+    "@meith/plugin-kit": "0.16.0",
+    "@meith/posts": "0.16.0",
+    "@meith/polls": "0.16.0",
+    "@meith/i18n": "0.16.0",
+    "@meith/reputation": "0.16.0",
+    "@meith/search": "0.16.0",
+    "@meith/signatures": "0.16.0",
+    "@meith/settings": "0.16.0",
+    "@meith/subscriptions": "0.16.0",
+    "@meith/theme-clubhouse": "0.16.0",
+    "@meith/relations": "0.16.0",
+    "@meith/messages": "0.16.0",
+    "@meith/runtime": "0.16.0",
+    "@meith/plugin-dues": "0.16.0",
+    "@meith/theme-kit": "0.16.0",
+    "@meith/tasks": "0.16.0",
+    "@meith/theme-midnight": "0.16.0",
+    "@meith/theme-default": "0.16.0",
+    "@meith/theme-phasebook": "0.16.0",
+    "@meith/theme-raidframe": "0.16.0",
+    "@meith/threads": "0.16.0",
+    "@meith/upgrade": "0.16.0",
+    "@meith/ui": "0.16.0"
+  },
+  "scripts": {
+    "dev": "next dev",
+    "build": "next build",
+    "start": "next start",
+    "lint": "biome check .",
+    "typecheck": "tsc -p tsconfig.json --noEmit"
+  }
+}

package/postcss.config.mjs

@@ -0,0 +1,7 @@
+const config = {
+  plugins: {
+    '@tailwindcss/postcss': {},
+  },
+}
+
+export default config