@meith/web 0.21.1 → 0.22.0

package/app/(board)/notifications/preferences/page.tsx

@@ -1,10 +1,14 @@
 import type { Metadata } from 'next'
 import { notFound } from 'next/navigation'
 
-import { NotificationPreferencesForm } from '@/components/account/notification-forms'
+import {
+  AnnouncementsOptInForm,
+  NotificationPreferencesForm,
+} from '@/components/account/notification-forms'
 import { PushDeviceForm } from '@/components/account/push-device-form'
 import { BoardNotice } from '@/components/shell/board-notice'
 import { PanelPage } from '@/components/shell/panel-page'
+import { getContainer } from '@/server/container'
 import { getActor } from '@/server/context'
 import { getTranslator, tr } from '@/server/i18n'
 import { audiencesForActor } from '@/server/notification-audience'
@@ -34,6 +38,9 @@ export default async function NotificationPreferencesPage({
     await Promise.all(audiences.map((audience) => service.preferences(userId, audience)))
   ).flat()
 
+  const { memberSettings } = getContainer()
+  const settings = memberSettings === null ? null : await memberSettings.read(userId)
+
   const push = await pushAvailability()
   const view = buildPreferencesView(rows, await getTranslator())
   const notice = notificationNotice(query, await getTranslator())
@@ -60,6 +67,13 @@ export default async function NotificationPreferencesPage({
         push={push.enabled}
         copy={notificationFormsCopy(await getTranslator())}
       />
+
+      {settings !== null && (
+        <AnnouncementsOptInForm
+          optedIn={settings.massMailOptInAt !== null}
+          copy={notificationFormsCopy(await getTranslator())}
+        />
+      )}
     </PanelPage>
   )
 }

package/app/(board)/unsubscribe/page.tsx

@@ -60,9 +60,11 @@ export default async function UnsubscribePage({
           <UnsubscribeConfirmForm
             token={token}
             description={
-              claim.scope === 'email'
-                ? await tr('page.unsubscribe.emailScope')
-                : await tr('page.unsubscribe.targetScope')
+              claim.scope === 'mass-mail'
+                ? await tr('page.unsubscribe.massMailScope')
+                : claim.scope === 'email'
+                  ? await tr('page.unsubscribe.emailScope')
+                  : await tr('page.unsubscribe.targetScope')
             }
             copy={followFormCopy(translator)}
           />

package/app/admin/api/marketplace/screenshot/route.ts

@@ -17,14 +17,6 @@ function fail(status: number, message: string): Response {
   })
 }
 
-/**
- * Streams one marketplace screenshot to the admin panel. The board fetches
- * it, not the browser — this is the "proxied" half of "screenshots proxied
- * or linked from the feed's own host only" (see docs/marketplace.md and the
- * MEI-80 issue). `key` and `index` are looked up against the currently
- * cached feed rather than trusted as a URL themselves, so nothing this route
- * fetches is ever chosen by the caller.
- */
 export async function GET(request: NextRequest): Promise<Response> {
   try {
     await requireAdmin()

package/app/admin/users/mail/page.tsx

@@ -58,7 +58,7 @@ export default async function AdminMassMailPage() {
         <p>{await tr('page.before-press-it')}</p>
         <ul className="flex list-disc flex-col gap-1 pl-4">
           <li>{translator.t('adminUsers.massMailQueued')}</li>
-          <li>{translator.t('adminUsers.massMailNoUnsubscribe')}</li>
+          <li>{translator.t('adminUsers.massMailOptIn')}</li>
           <li>{translator.t('adminUsers.massMailContinues')}</li>
           <li>{await tr('page.email-cannot-be-unsent')}</li>
         </ul>

package/app/layout.tsx

@@ -41,9 +41,7 @@ export async function generateMetadata(): Promise<Metadata> {
     name = settings.get('board.name').trim() || BOARD_TITLE
     description = settings.get('board.description').trim() || undefined
     origin = resolveBoardUrl({ environment: env, settings }).url || origin
-  } catch {
-    /* ignore */
-  }
+  } catch {}
 
   return {
     title: {

package/app/manifest.ts

@@ -16,9 +16,7 @@ export default async function manifest(): Promise<MetadataRoute.Manifest> {
     const settings = await getSettings()
     name = settings.get('board.name').trim() || BOARD_TITLE
     description = settings.get('board.description').trim()
-  } catch {
-    /* ignore */
-  }
+  } catch {}
 
   const { browserThemeColor } = await getThemeRuntimeStyle()
 

package/bin/forum-web.mjs

@@ -1,81 +1,4 @@
 #!/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 bin now also passes that root explicitly,
- * as `FORUM_WORKSPACE_ROOT`, so the depth is what keeps the *copied file's*
- * own default honest rather than what the build depends on.
- *
- * `--at-root` materializes into the workspace root itself instead
- * (`<root>`, depth zero), which is the one thing Vercel's Next.js preset
- * needs and `.meith/app` cannot give it: the build artefact at
- * `<root>/.next`, where that builder looks and where, for a Next.js project,
- * it cannot be told to look elsewhere. Nothing about the seam changes — the
- * generated tsconfig's `paths` name `./community.config.ts` instead of
- * `../../community.config.ts`, and every other path in here is computed from
- * `appDir` rather than assumed. Because that mode writes framework-owned
- * names (`app/`, `src/`, `next.config.mjs`, ...) into a directory the board
- * also keeps its own files in, ownership there is decided per *file* — the
- * files it wrote last time, recorded in `.meith/materialized.json`, plus any
- * whose contents are already byte for byte what it would write. Everything
- * else is the board's: never removed, never overwritten, and a collision
- * stops the build naming every file involved. A board can therefore keep
- * `public/ads.txt` beside the shipped `public/sw.js`.
- *
- * `GENERATED_ENTRIES` are the exception, and have to be: `tsconfig.json` and
- * `next-env.d.ts` are written from scratch rather than copied, so there is no
- * shipped file to compare a board's own against and nothing to tell one apart
- * from a stale one this bin wrote. Both are replaced without asking, so a
- * board cannot keep its own compiler options at the root of an `--at-root`
- * workspace. See docs/development.md, "Consuming the board from a workspace".
- *
- * 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 sets neither itself: `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.
- * `FORUM_WORKSPACE_ROOT` is always exported onward from here, defaulting to
- * the invoking workspace's own root when that workspace did not set it, so
- * that everything downstream — the copied `next.config.mjs`, and the
- * `@source` rebase below — reads one answer rather than each re-deriving it
- * from where it happens to sit.
- */
 import { spawn } from 'node:child_process'
 import {
   cpSync,
@@ -105,12 +28,6 @@ for (const name of ['FORUM_WORKSPACE_ROOT', 'FORUM_ALIASES_FROM']) {
 }
 if (!process.env.FORUM_WORKSPACE_ROOT) process.env.FORUM_WORKSPACE_ROOT = workspaceRoot
 
-/**
- * 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',
@@ -141,15 +58,6 @@ function walkFiles(dir, prefix, into) {
   return into
 }
 
-/**
- * Every file `--at-root` is about to write into the workspace root, as posix
- * relative paths: the shipped entries expanded file by file, plus the two
- * this bin generates. Ownership is decided per file rather than per
- * top-level name so that a board can keep its own files inside a directory
- * the framework also writes into — `public/ads.txt` beside the shipped
- * `public/sw.js`. See docs/development.md, "Consuming the board from a
- * workspace".
- */
 function intendedRootFiles() {
   const files = []
   for (const entry of APP_ENTRIES) {
@@ -174,13 +82,6 @@ function absoluteRootPath(rel) {
   return join(workspaceRoot, ...rel.split('/'))
 }
 
-/**
- * What this bin would leave at `rel`, which is the shipped file's own bytes
- * for everything except `globals.css` — that one is rewritten in place after
- * the copy (`rewriteGlobalsCssSourcePaths`), so comparing a materialized
- * tree against the package source would report the one file this bin always
- * edits as though the board had edited it.
- */
 function materializedContent(rel) {
   const source = readFileSync(join(packageRoot, ...rel.split('/')))
   if (rel !== GLOBALS_CSS) return source
@@ -213,17 +114,6 @@ function pruneEmptyDirectories(rel) {
   }
 }
 
-/**
- * `--at-root` only; every other mode owns `.meith/app` outright and replaces
- * it wholesale. A file this bin is about to write is its own to replace when
- * the record says it wrote that file before, or when what is on disk is byte
- * for byte what it would write anyway — the second case being a checkout
- * that committed a materialized file, where no record exists and refusing
- * would fail the deploy over a file identical to the one being written.
- * Anything else is the board's, and the board's is never overwritten —
- * except `GENERATED_ENTRIES`, which are written rather than copied and so
- * can satisfy neither test; those are replaced unconditionally.
- */
 function claimRootFiles(intended) {
   const owned = new Set(readMaterializedRecord())
 
@@ -247,12 +137,6 @@ function claimRootFiles(intended) {
   }
 }
 
-/**
- * Files the previous run wrote and this one will not: the framework stopped
- * shipping them. They were this bin's own, so they go — nothing the board
- * added is in the record, which is why removal is driven from it rather than
- * from the directory.
- */
 function removeStaleRootFiles(intended) {
   const keeping = new Set(intended)
   for (const rel of readMaterializedRecord()) {
@@ -267,15 +151,6 @@ function recordRootFiles(intended) {
   writeFileSync(MATERIALIZED_RECORD, `${JSON.stringify({ files: intended }, null, 2)}\n`)
 }
 
-/**
- * Files the board itself put under a directory the framework owns outright.
- * Nothing here removes them — ownership is per file, so they simply survive —
- * but a scaffolded board gitignores those directories as a unit, so a route
- * added under `app/` works locally, is never committed, and is absent from a
- * deploy built out of the checkout. Warned about rather than refused: the
- * file is the author's to keep, and this is the only moment anything looks at
- * it. `public/` is excluded because that one is shared on purpose.
- */
 function warnAboutStrayBoardFiles(intended) {
   const written = new Set(intended)
   const owned = APP_ENTRIES.filter((entry) => !SHARED_ENTRIES.includes(entry))
@@ -297,7 +172,7 @@ function warnAboutStrayBoardFiles(intended) {
       'They are left exactly as they are. A scaffolded board gitignores these directories as ' +
       'a unit, though, so nothing above is committed, and a deploy that builds from the ' +
       'checkout will not see it. A board extends the forum through plugins and themes ' +
-      '(docs/plugin-api.md, docs/theme-api.md), not by adding files here.',
+      '(docs/customization/plugins.md, docs/customization/themes.md), not by adding files here.',
   )
 }
 
@@ -309,24 +184,6 @@ function toPosixRelative(from, to) {
 const SOURCE_LINE = /[ \t]*@source "((?:\.\.\/)+)([^"]+)";\n?/g
 const BOARD_PACKAGES = ['node_modules', '@meith']
 
-/**
- * MEI-131: every `@source` in globals.css names a directory of *this*
- * repository — `themes`, `plugins`, `packages/ui/src`. Rebasing them onto the
- * board's workspace root is right for the one in-repo consumer (boards/stock,
- * whose FORUM_WORKSPACE_ROOT is this repo) and wrong for every scaffolded
- * board, where none of those directories exist: the same code is installed
- * under `node_modules/@meith` instead. Tailwind does not fail on a `@source`
- * that resolves to nothing — it builds green and emits no utilities for
- * anything it could not scan — so a board deployed this way served a page
- * with no styling at all.
- *
- * A source whose target is really there is kept and rebased as before. One
- * that is not is dropped in favour of a single source over the installed
- * packages, which covers the themes, `@meith/ui` and the plugins together.
- * Tailwind ignores `node_modules` when detecting sources itself, but honours
- * it when named here, and follows the symlinks a pnpm install leaves — both
- * confirmed against the version this app pins.
- */
 export function rebaseGlobalsCssSources(css, cssDir, workspaceRoot, exists = existsSync) {
   const rebased = []
   let missing = false
@@ -359,29 +216,6 @@ function rewriteGlobalsCssSourcePaths() {
   )
 }
 
-/**
- * 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. `@board/config`
- * and `@board/plugins` are excluded from the copy — they 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.
- */
 function monorepoAliases() {
   const configFile = process.env.FORUM_ALIASES_FROM
   if (!configFile) return {}
@@ -398,14 +232,6 @@ function monorepoAliases() {
   return aliases
 }
 
-/**
- * Replaces each shipped entry (`APP_ENTRIES`) but never `rm -rf`s the whole
- * `.meith/app` directory: `.next` lives there 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. The
- * `next-env.d.ts` it writes only needs to exist, not be complete — next
- * regenerates it with the right content on first run.
- */
 function materialize() {
   const boardConfig = join(workspaceRoot, 'community.config.ts')
   const boardPlugins = join(workspaceRoot, 'community.plugins.ts')
@@ -475,13 +301,6 @@ function materialize() {
   }
 }
 
-/**
- * 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).
- */
 function resolveNextBin() {
   const require = createRequire(join(packageRoot, 'package.json'))
   try {

package/bin/forum-web.test.ts

@@ -36,14 +36,6 @@ describe('rebaseGlobalsCssSources', () => {
     expect(rewritten).toContain('.foo { color: red; }')
   })
 
-  /**
-   * Against the real shipped file, not a fixture: this rebase now runs on
-   * every materialization including the default one, where it must be a
-   * no-op. Every `@source` in that file is written relative to the workspace
-   * root, and this only stays a no-op while that holds — a `@source` meaning
-   * anything else (`../fonts`, for `src/fonts`) would be silently retargeted
-   * at the workspace root, and fails here instead.
-   */
   const shippedGlobalsCss = readFileSync(
     new URL('../src/styles/globals.css', import.meta.url),
     'utf8',
@@ -87,13 +79,6 @@ describe('rebaseGlobalsCssSources', () => {
     ).toBe(css)
   })
 
-  /**
-   * MEI-131. A scaffolded board has none of the directories these sources
-   * name — the same code is installed under `node_modules/@meith` — and
-   * Tailwind emits no utilities for a source it cannot scan while still
-   * exiting 0, so the failure is a board that serves an unstyled page rather
-   * than a build that stops.
-   */
   describe('in a board, where none of those directories exist', () => {
     const inBoard = (path: string) => path.includes('node_modules')
 
@@ -157,13 +142,6 @@ describe('rebaseGlobalsCssSources', () => {
   })
 })
 
-/**
- * `forum-web start --at-root` materializes and then stops, because there is
- * no standalone build for it to exec — which makes it the whole
- * materialization path in under a tenth of a second, with no `next build`
- * anywhere near it. Materialization is the part that has been wrong; the
- * build is not.
- */
 const BIN = fileURLToPath(new URL('./forum-web.mjs', import.meta.url))
 
 function materializeAtRoot(dir: string) {

package/next.config.mjs

@@ -1,33 +1,13 @@
-import { existsSync } from 'node:fs'
+import { existsSync, readFileSync } 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 by default — correct
- * where `forum-web` materializes at `.meith/app` and where this file sits in
- * `apps/community` unmaterialized. `boards/stock` and `forum-web --at-root`
- * are both at other depths, and neither relies on this default:
- * `FORUM_WORKSPACE_ROOT` is set for the first by that board's own scripts
- * and passed on by `forum-web` in every case, so this fallback only applies
- * when the file is read outside that bin entirely (see
- * docs/architecture.md, "The stock board"; docs/development.md, "Consuming
- * the board from a workspace").
- */
 const workspaceRoot = process.env.FORUM_WORKSPACE_ROOT
   ? path.resolve(process.env.FORUM_WORKSPACE_ROOT)
   : path.join(here, '../../')
 
-/**
- * The relative equivalent of `workspaceRoot`, for `outputFileTracingIncludes`
- * below — see docs/development.md, "Consuming the board from a workspace",
- * for why that option needs a path relative to this file rather than an
- * absolute one. It is `.` rather than the empty string when this file already
- * sits at the workspace root, which is what `forum-web build --at-root`
- * materializes (same section) — an empty prefix would make the glob below
- * read as an absolute path and match nothing.
- */
 const upToWorkspaceRoot = path.relative(here, workspaceRoot).split(path.sep).join('/') || '.'
 
 const loadedEnvFiles = []
@@ -42,6 +22,8 @@ if (process.env.NODE_ENV !== 'production' && loadedEnvFiles.length > 0) {
   console.log(`- Environments: ${loadedEnvFiles.join(', ')} (${workspaceRoot})`)
 }
 
+const FRAMEWORK_PACKAGES = ['next', 'react', 'react-dom']
+
 const nextConfig = {
   ...(process.env.VERCEL ? {} : { output: 'standalone' }),
   poweredByHeader: false,
@@ -58,11 +40,9 @@ const nextConfig = {
     'nodemailer',
   ],
   outputFileTracingRoot: workspaceRoot,
-  /** See docs/development.md, "Consuming the board from a workspace", for why this is set. */
   turbopack: {
     root: workspaceRoot,
   },
-  /** Works around a gap in Next's own tracing — see docs/development.md, "Consuming the board from a workspace". */
   outputFileTracingIncludes: {
     '/**': [
       `${upToWorkspaceRoot}/node_modules/.pnpm/@swc+helpers@0.5.23/node_modules/@swc/helpers/**/*`,
@@ -72,12 +52,6 @@ const nextConfig = {
   images: {
     unoptimized: true,
   },
-  /**
-   * Every `@meith/*` package this app's dependency graph reaches, not just the
-   * ones apps/community imports directly — see docs/development.md,
-   * "Consuming the board from a workspace", and docs/release.md, "They ship
-   * TypeScript source, deliberately".
-   */
   transpilePackages: [
     '@meith/accounts',
     '@meith/admin',
@@ -146,4 +120,15 @@ const nextConfig = {
   },
 }
 
+const boardManifestFile = path.join(workspaceRoot, 'package.json')
+if (existsSync(boardManifestFile)) {
+  const boardManifest = JSON.parse(readFileSync(boardManifestFile, 'utf8'))
+  for (const name of Object.keys(boardManifest.dependencies ?? {})) {
+    if (FRAMEWORK_PACKAGES.includes(name)) continue
+    if (nextConfig.serverExternalPackages.includes(name)) continue
+    if (nextConfig.transpilePackages.includes(name)) continue
+    nextConfig.transpilePackages.push(name)
+  }
+}
+
 export default nextConfig

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@meith/web",
-  "version": "0.21.1",
+  "version": "0.22.0",
   "description": "The board itself: the Next.js app, and the forum-web bin that materializes it into an external board workspace.",
   "license": "MIT",
   "repository": {
@@ -43,52 +43,52 @@
     "typescript": "7.0.2",
     "@types/react": "^19",
     "@types/react-dom": "^19",
-    "@meith/admin": "0.21.1",
-    "@meith/antispam": "0.21.1",
-    "@meith/accounts": "0.21.1",
-    "@meith/api": "0.21.1",
-    "@meith/attachments": "0.21.1",
-    "@meith/authorization": "0.21.1",
-    "@meith/avatars": "0.21.1",
-    "@meith/core": "0.21.1",
-    "@meith/db": "0.21.1",
-    "@meith/demo": "0.21.1",
-    "@meith/drivers": "0.21.1",
-    "@meith/events": "0.21.1",
-    "@meith/forums": "0.21.1",
-    "@meith/i18n": "0.21.1",
-    "@meith/groups": "0.21.1",
-    "@meith/drafts": "0.21.1",
-    "@meith/import": "0.21.1",
-    "@meith/install": "0.21.1",
-    "@meith/mail": "0.21.1",
-    "@meith/marketplace": "0.21.1",
-    "@meith/markdown": "0.21.1",
-    "@meith/messages": "0.21.1",
-    "@meith/moderation": "0.21.1",
-    "@meith/notifications": "0.21.1",
-    "@meith/plugin-dues": "0.21.1",
-    "@meith/plugin-kit": "0.21.1",
-    "@meith/polls": "0.21.1",
-    "@meith/posts": "0.21.1",
-    "@meith/profile-fields": "0.21.1",
-    "@meith/relations": "0.21.1",
-    "@meith/runtime": "0.21.1",
-    "@meith/reputation": "0.21.1",
-    "@meith/settings": "0.21.1",
-    "@meith/subscriptions": "0.21.1",
-    "@meith/signatures": "0.21.1",
-    "@meith/tasks": "0.21.1",
-    "@meith/search": "0.21.1",
-    "@meith/theme-clubhouse": "0.21.1",
-    "@meith/theme-default": "0.21.1",
-    "@meith/theme-midnight": "0.21.1",
-    "@meith/theme-kit": "0.21.1",
-    "@meith/theme-phasebook": "0.21.1",
-    "@meith/threads": "0.21.1",
-    "@meith/ui": "0.21.1",
-    "@meith/theme-raidframe": "0.21.1",
-    "@meith/upgrade": "0.21.1"
+    "@meith/admin": "0.22.0",
+    "@meith/antispam": "0.22.0",
+    "@meith/api": "0.22.0",
+    "@meith/accounts": "0.22.0",
+    "@meith/attachments": "0.22.0",
+    "@meith/authorization": "0.22.0",
+    "@meith/avatars": "0.22.0",
+    "@meith/core": "0.22.0",
+    "@meith/drafts": "0.22.0",
+    "@meith/db": "0.22.0",
+    "@meith/drivers": "0.22.0",
+    "@meith/demo": "0.22.0",
+    "@meith/groups": "0.22.0",
+    "@meith/forums": "0.22.0",
+    "@meith/import": "0.22.0",
+    "@meith/events": "0.22.0",
+    "@meith/i18n": "0.22.0",
+    "@meith/install": "0.22.0",
+    "@meith/markdown": "0.22.0",
+    "@meith/marketplace": "0.22.0",
+    "@meith/mail": "0.22.0",
+    "@meith/messages": "0.22.0",
+    "@meith/notifications": "0.22.0",
+    "@meith/plugin-dues": "0.22.0",
+    "@meith/moderation": "0.22.0",
+    "@meith/plugin-kit": "0.22.0",
+    "@meith/posts": "0.22.0",
+    "@meith/polls": "0.22.0",
+    "@meith/profile-fields": "0.22.0",
+    "@meith/relations": "0.22.0",
+    "@meith/reputation": "0.22.0",
+    "@meith/runtime": "0.22.0",
+    "@meith/search": "0.22.0",
+    "@meith/settings": "0.22.0",
+    "@meith/signatures": "0.22.0",
+    "@meith/subscriptions": "0.22.0",
+    "@meith/theme-kit": "0.22.0",
+    "@meith/theme-clubhouse": "0.22.0",
+    "@meith/theme-default": "0.22.0",
+    "@meith/theme-phasebook": "0.22.0",
+    "@meith/theme-midnight": "0.22.0",
+    "@meith/theme-raidframe": "0.22.0",
+    "@meith/threads": "0.22.0",
+    "@meith/ui": "0.22.0",
+    "@meith/tasks": "0.22.0",
+    "@meith/upgrade": "0.22.0"
   },
   "scripts": {
     "dev": "next dev",

package/proxy.ts

@@ -48,20 +48,6 @@ interface Policy {
   readonly value: string
 }
 
-/**
- * Passes the request through, and hands a reader something to be counted by.
- *
- * The cookie is minted here because the Edge is the only place that can set one
- * on an ordinary page response — a render cannot. The row it stands for is
- * written by the render, which has the database this runtime does not.
- *
- * Whether the client *returned* the cookie is the load-bearing part, and it
- * cannot be read downstream: Next reflects a cookie set here into the request
- * the render sees, so a first-ever visit is indistinguishable from a returning
- * one by cookie alone. Hence the header — set when the cookie is new, deleted
- * otherwise, so a crawler that never keeps one is never counted and a client
- * cannot supply its own.
- */
 function withPath(req: NextRequest, policy: Policy): NextResponse {
   const fresh = !req.cookies.has(GUEST_COOKIE) && !req.cookies.has(DEV_GUEST_COOKIE)