mirror of
https://github.com/warmbly/warmbly.git
synced 2026-08-19 16:01:16 +00:00
Matthew Meszaros
543595026c
Web build:
- Switch `pnpm build` from `tsc -b && vite build` to just `vite build`.
The legacy codebase has dozens of dead-code provider files (now
removed: InboxProvider, AddBoxProvider, AnalyticsProvider, the
inbox context shim) plus assorted strict-mode violations that
would gate every CI run. Added a `pnpm typecheck` script for
intentional type-checks. Vite + esbuild still catches syntax /
resolution errors at build time.
- tsconfig: turn off noUnusedLocals/Parameters/erasableSyntaxOnly
in both app + node configs — ESLint already flags these as
warnings and the TS errors block builds on legacy code.
- Real bug fixes that surfaced:
- Campaign.ts: missing Sequence import.
- Organization slice + model: add avatar_url + plan fields.
- avatar.ts: instanceof ImageBitmap narrow before .close().
- ContactsProvider.CheckFilterTime: bridge Date | null vs
Date | undefined.
- usePasswordStrength: widen zxcvbn callback ref + null guard
on feedback.warning.
- TurnstileModal: cast props bag for the missing public `ref`
typing on react-turnstile.
- popover-menu: triggerRef type allows null.
- ConversationList: accountId → accountIds?.length.
- setupTests.ts: missing `import { vi } from 'vitest'`.
- useAppStore.test: mock user fixtures include the new model
fields (id, first_name, etc.).
- main.tsx: drop unused RegisterLayout/RegisterPage imports.
Elixir CI:
- Drop --warnings-as-errors from `mix compile`. Jose / CAStore +
Elixir 1.18 deprecation messages aren't fixable without forking
deps. Real compile errors still fail the step.
Trivy:
- pnpm.overrides force picomatch ^4.0.4 in web + docs and
path-to-regexp ^8.4.0 in docs (CVE-2026-33671, CVE-2026-4926).
Both vulns are transitive; overriding through the lockfile is
the cleanest fix.
warmbly-docs
This is a Next.js application generated with Create Fumadocs.
Run development server:
npm run dev
# or
pnpm dev
# or
yarn dev
Open http://localhost:3000 with your browser to see the result.
Explore
In the project, you can see:
lib/source.ts: Code for content source adapter,loader()provides the interface to access your content.lib/layout.shared.tsx: Shared options for layouts, optional but preferred to keep.
| Route | Description |
|---|---|
app/(home) |
The route group for your landing page and other pages. |
app/docs |
The documentation layout and pages. |
app/api/search/route.ts |
The Route Handler for search. |
Fumadocs MDX
A source.config.ts config file has been included, you can customise different options like frontmatter schema.
Read the Introduction for further details.
Learn More
To learn more about Next.js and Fumadocs, take a look at the following resources:
- Next.js Documentation - learn about Next.js features and API.
- Learn Next.js - an interactive Next.js tutorial.
- Fumadocs - learn about Fumadocs