@jant/core 0.2.20 → 0.3.0

package/bin/jant.js

@@ -7,12 +7,9 @@
  *   swizzle <component> [--wrap|--eject]  - Override a theme component
  */
 
-import { readFileSync, writeFileSync, mkdirSync, existsSync } from "fs";
-import { resolve, dirname } from "path";
-import { fileURLToPath } from "url";
+import {  writeFileSync, mkdirSync, existsSync } from "fs";
+import { resolve } from "path";
 
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
 
 // Available components that can be swizzled
 const SWIZZLABLE_COMPONENTS = {

package/dist/auth.d.ts

@@ -14,6 +14,7 @@ export declare function createAuth(d1: D1Database, options: {
         minPasswordLength: number;
     };
     session: {
+        expiresIn: number;
         cookieCache: {
             enabled: true;
             maxAge: number;

package/dist/auth.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"auth.d.ts","sourceRoot":"","sources":["../src/auth.ts"],"names":[],"mappings":"AAAA;;GAEG;AAOH,wBAAgB,UAAU,CACxB,EAAE,EAAE,UAAU,EACd,OAAO,EAAE;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE;;;;;;;;;;;;;;;GA4B7C;AAED,MAAM,MAAM,IAAI,GAAG,UAAU,CAAC,OAAO,UAAU,CAAC,CAAC"}
+{"version":3,"file":"auth.d.ts","sourceRoot":"","sources":["../src/auth.ts"],"names":[],"mappings":"AAAA;;GAEG;AAOH,wBAAgB,UAAU,CACxB,EAAE,EAAE,UAAU,EACd,OAAO,EAAE;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,OAAO,EAAE,MAAM,CAAA;CAAE;;;;;;;;;;;;;;;;GA6B7C;AAED,MAAM,MAAM,IAAI,GAAG,UAAU,CAAC,OAAO,UAAU,CAAC,CAAC"}

package/dist/auth.js

@@ -26,6 +26,7 @@ export function createAuth(d1, options) {
             minPasswordLength: 8
         },
         session: {
+            expiresIn: 3600 * 24 * 365 * 10,
             cookieCache: {
                 enabled: true,
                 maxAge: 60 * 5

package/dist/lib/schemas.d.ts

@@ -58,7 +58,7 @@ export declare const CreatePostSchema: z.ZodObject<{
         unlisted: "unlisted";
         draft: "draft";
     }>;
-    sourceUrl: z.ZodUnion<[z.ZodOptional<z.ZodString>, z.ZodLiteral<"">]>;
+    sourceUrl: z.ZodUnion<[z.ZodOptional<z.ZodURL>, z.ZodLiteral<"">]>;
     sourceName: z.ZodOptional<z.ZodString>;
     path: z.ZodUnion<[z.ZodOptional<z.ZodString>, z.ZodLiteral<"">]>;
     replyToId: z.ZodOptional<z.ZodString>;
@@ -84,7 +84,7 @@ export declare const UpdatePostSchema: z.ZodObject<{
         unlisted: "unlisted";
         draft: "draft";
     }>>;
-    sourceUrl: z.ZodOptional<z.ZodUnion<[z.ZodOptional<z.ZodString>, z.ZodLiteral<"">]>>;
+    sourceUrl: z.ZodOptional<z.ZodUnion<[z.ZodOptional<z.ZodURL>, z.ZodLiteral<"">]>>;
     sourceName: z.ZodOptional<z.ZodOptional<z.ZodString>>;
     path: z.ZodOptional<z.ZodUnion<[z.ZodOptional<z.ZodString>, z.ZodLiteral<"">]>>;
     replyToId: z.ZodOptional<z.ZodOptional<z.ZodString>>;

package/dist/lib/schemas.js

@@ -30,7 +30,7 @@ import { POST_TYPES, VISIBILITY_LEVELS } from "../types.js";
     title: z.string().optional(),
     content: z.string(),
     visibility: VisibilitySchema,
-    sourceUrl: z.string().url().optional().or(z.literal("")),
+    sourceUrl: z.url().optional().or(z.literal("")),
     sourceName: z.string().optional(),
     path: z.string().regex(/^[a-z0-9-]*$/).optional().or(z.literal("")),
     replyToId: z.string().optional(),

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jant/core",
-  "version": "0.2.20",
+  "version": "0.3.0",
   "description": "A modern, open-source microblogging platform built on Cloudflare Workers",
   "type": "module",
   "bin": {
@@ -8,15 +8,15 @@
   },
   "exports": {
     ".": {
-      "types": "./dist/index.d.ts",
+      "types": "./src/index.ts",
       "default": "./dist/index.js"
     },
     "./theme": {
-      "types": "./dist/theme/index.d.ts",
+      "types": "./src/theme/index.ts",
       "default": "./dist/theme/index.js"
     },
     "./i18n": {
-      "types": "./dist/i18n/index.d.ts",
+      "types": "./src/i18n/index.ts",
       "default": "./dist/i18n/index.js"
     },
     "./preset.css": "./src/preset.css",
@@ -49,6 +49,7 @@
   "devDependencies": {
     "@cloudflare/workers-types": "^4.20260131.0",
     "@lingui/cli": "^5.9.0",
+    "@lingui/conf": "^5.9.0",
     "@lingui/format-po": "^5.9.0",
     "@lingui/swc-plugin": "^5.10.1",
     "@swc/cli": "^0.6.0",

package/src/auth.ts

@@ -31,6 +31,7 @@ export function createAuth(
       minPasswordLength: 8,
     },
     session: {
+      expiresIn: 3600 * 24 * 365 * 10, // 10 years
       cookieCache: {
         enabled: true,
         maxAge: 60 * 5, // 5 minutes

package/src/lib/schemas.ts

@@ -37,7 +37,7 @@ export const CreatePostSchema = z.object({
   title: z.string().optional(),
   content: z.string(),
   visibility: VisibilitySchema,
-  sourceUrl: z.string().url().optional().or(z.literal("")),
+  sourceUrl: z.url().optional().or(z.literal("")),
   sourceName: z.string().optional(),
   path: z
     .string()

package/src/i18n/EXAMPLES.md

@@ -1,257 +0,0 @@
-# i18n Usage Examples
-
-## New API: useLingui() Hook
-
-We now use a React-like hook API that eliminates prop drilling and makes code cleaner.
-
-### Basic Pattern
-
-```tsx
-import { I18nProvider, useLingui } from "@/i18n";
-
-// 1. Wrap your app in route handler
-dashRoute.get("/", async (c) => {
-  return c.html(
-    <I18nProvider c={c}>
-      <MyApp />
-    </I18nProvider>,
-  );
-});
-
-// 2. Use useLingui() hook inside components
-function MyApp() {
-  const { t } = useLingui();
-
-  return (
-    <h1>{t({ message: "Dashboard", comment: "@context: Page title" })}</h1>
-  );
-}
-```
-
-### Why the `comment` field?
-
-The `comment` field provides context for AI translators, improving translation quality:
-
-```tsx
-// ✅ Good - clear context
-t({ message: "Dashboard", comment: "@context: Page title" });
-t({ message: "Dashboard", comment: "@context: Navigation link" });
-
-// ❌ Bad - no context (translator might choose wrong word)
-t({ message: "Dashboard" });
-```
-
----
-
-## Complete Example
-
-```tsx
-import { I18nProvider, useLingui, Trans } from "@/i18n";
-
-// Route handler: wrap in I18nProvider
-dashRoute.get("/", async (c) => {
-  const posts = await c.var.services.posts.list();
-
-  return c.html(
-    <I18nProvider c={c}>
-      <Dashboard postCount={posts.length} username="Alice" />
-    </I18nProvider>,
-  );
-});
-
-// Component: use useLingui() hook
-function Dashboard({
-  postCount,
-  username,
-}: {
-  postCount: number;
-  username: string;
-}) {
-  const { t } = useLingui();
-
-  return (
-    <div>
-      {/* 1. Simple translation */}
-      <h1>{t({ message: "Dashboard", comment: "@context: Page title" })}</h1>
-
-      {/* 2. With variables */}
-      <p>
-        {t(
-          {
-            message: "Welcome back, {name}!",
-            comment: "@context: Welcome message",
-          },
-          { name: username },
-        )}
-      </p>
-
-      {/* 3. With dynamic values */}
-      <p>
-        {t(
-          {
-            message: "You have {count} posts",
-            comment: "@context: Post count",
-          },
-          { count: postCount },
-        )}
-      </p>
-
-      {/* 4. With embedded components */}
-      <p>
-        <Trans comment="@context: Help text">
-          Read the{" "}
-          <a href="/docs" class="underline">
-            documentation
-          </a>{" "}
-          for help
-        </Trans>
-      </p>
-    </div>
-  );
-}
-```
-
----
-
-## Trans Component: Embedded JSX
-
-The `Trans` component is a simplified implementation that renders children as-is. It's useful for translations with embedded links or formatting.
-
-```tsx
-import { Trans } from "@/i18n";
-
-// Simple link
-<Trans comment="@context: Website link">
-  Visit <a href="/" class="text-primary">our website</a>
-</Trans>
-
-// Multiple elements
-<Trans comment="@context: Learn more link">
-  Click <strong class="font-bold">here</strong> to <a href="/learn" class="underline">learn more</a>
-</Trans>
-
-// With formatting
-<Trans comment="@context: Welcome message">
-  Welcome <strong class="font-semibold">back</strong>!
-</Trans>
-```
-
-**Note**: This is a simplified implementation that renders children directly. For complex translations with dynamic placeholders, use the `t()` function instead:
-
-```tsx
-const { t } = useLingui();
-
-// For dynamic content, use t() with placeholders
-<p>
-  {t(
-    {
-      message: "Visit {linkStart}our website{linkEnd}",
-      comment: "@context: Website link",
-    },
-    {
-      linkStart: '<a href="/" class="text-primary">',
-      linkEnd: "</a>",
-    },
-  )}
-</p>;
-```
-
----
-
-## Comparison: Before vs Now
-
-### Before (Prop drilling required)
-
-```tsx
-import { getI18n } from "@/i18n";
-
-dashRoute.get("/", async (c) => {
-  const i18n = getI18n(c);
-
-  return c.html(
-    <Layout>
-      <MyComponent c={c} /> {/* Must pass c prop */}
-    </Layout>,
-  );
-});
-
-function MyComponent({ c }: { c: Context }) {
-  const i18n = getI18n(c);
-  const title = i18n._({ message: "Dashboard", comment: "@context: Title" });
-  const greeting = i18n._(
-    { message: "Hello {name}", comment: "@context: Greeting" },
-    { name: "Alice" },
-  );
-
-  return <h1>{title}</h1>;
-}
-```
-
-### Now (No prop drilling)
-
-```tsx
-import { I18nProvider, useLingui } from "@/i18n";
-
-dashRoute.get("/", async (c) => {
-  return c.html(
-    <I18nProvider c={c}>
-      <Layout>
-        <MyComponent /> {/* No props needed */}
-      </Layout>
-    </I18nProvider>,
-  );
-});
-
-function MyComponent() {
-  const { t } = useLingui();
-  const title = t({ message: "Dashboard", comment: "@context: Title" });
-  const greeting = t(
-    { message: "Hello {name}", comment: "@context: Greeting" },
-    { name: "Alice" },
-  );
-
-  return <h1>{title}</h1>;
-}
-```
-
----
-
-## Best Practices
-
-1. **Always wrap in I18nProvider**: Wrap your app in `<I18nProvider c={c}>` in route handlers
-2. **Use useLingui() hook**: Call `const { t } = useLingui()` inside components
-3. **Always include comment**: Provide `@context:` comment for better AI translations
-4. **Variables as second param**: `t({ message: "Hello {name}", comment: "..." }, { name })`
-5. **Use Trans for embedded JSX**: Use `<Trans>` for links and formatting
-6. **Extract translations**: Run `pnpm i18n:extract` after adding new strings
-7. **Compile translations**: Run `pnpm i18n:compile` to generate catalog files
-
----
-
-## Common Questions
-
-### Q: Why can't I use `t("Dashboard")` directly?
-
-A: Lingui uses a build-time extraction process. The `t()` function expects a message descriptor object that gets transformed by Lingui's macro system during the build. If you pass a plain string, the extraction tool won't be able to find and extract the message for translation.
-
-You must use the object syntax:
-
-```tsx
-t({ message: "Dashboard", comment: "@context: Page title" });
-```
-
-### Q: Can I use Lingui's official Trans component?
-
-A: Lingui's `Trans` component is designed for React and requires React Context. Since we use Hono JSX (not React), we provide a simplified `Trans` component that works with our SSR setup. It renders children directly without complex transformation.
-
-### Q: Why use useLingui() instead of getI18n(c)?
-
-A: The `useLingui()` hook provides a cleaner API that eliminates prop drilling. Instead of passing the Hono context `c` to every component, you wrap your app once in `I18nProvider` and all child components can access i18n via the hook.
-
-### Q: Is this safe for concurrent requests?
-
-A: Yes! Each request creates its own i18n instance via `I18nProvider`. The global state is only used during the synchronous rendering phase, so there's no risk of race conditions between concurrent requests.
-
-### Q: What if I call useLingui() outside I18nProvider?
-
-A: You'll get an error: "useLingui() called outside of I18nProvider". This is intentional - the hook must be used within the provider context. Always wrap your app in `<I18nProvider c={c}>` in your route handlers.

package/src/i18n/README.md

@@ -1,310 +0,0 @@
-# Jant i18n - React-like API for Hono JSX
-
-## ✅ API Overview
-
-We provide a React-like i18n API that works with Hono JSX SSR!
-
-### 1. **I18nProvider** - Like React Context Provider
-
-```tsx
-import { I18nProvider } from "@/i18n";
-
-// Wrap your app in route handler
-dashRoute.get("/", async (c) => {
-  return c.html(
-    <I18nProvider c={c}>
-      <YourApp />
-    </I18nProvider>,
-  );
-});
-```
-
-### 2. **useLingui()** - Like React hook
-
-```tsx
-import { useLingui } from "@/i18n";
-
-function MyComponent() {
-  // React-like hook API
-  const { t } = useLingui();
-
-  return (
-    <div>
-      {/* Simple and clean */}
-      <h1>{t({ message: "Dashboard", comment: "@context: Page title" })}</h1>
-    </div>
-  );
-}
-```
-
-### 3. **Trans Component** - For Embedded JSX
-
-```tsx
-import { Trans } from "@/i18n";
-
-function MyComponent() {
-  return (
-    <Trans comment="@context: Help text">
-      Read the <a href="/docs">documentation</a>
-    </Trans>
-  );
-}
-```
-
----
-
-## 📝 Complete Example
-
-```tsx
-/**
- * Dashboard Route - React-like i18n API
- */
-
-import { Hono } from "hono";
-import { I18nProvider, useLingui, Trans } from "@/i18n";
-
-export const dashRoute = new Hono();
-
-// Component: use useLingui() hook
-function DashboardContent({ postCount }: { postCount: number }) {
-  const { t } = useLingui();
-
-  return (
-    <div>
-      {/* 1. Simple translation */}
-      <h1>{t({ message: "Dashboard", comment: "@context: Page title" })}</h1>
-
-      {/* 2. With variables */}
-      <p>
-        {t(
-          {
-            message: "You have {count} posts",
-            comment: "@context: Post count message",
-          },
-          { count: postCount },
-        )}
-      </p>
-
-      {/* 3. With embedded components - use Trans */}
-      <p>
-        <Trans comment="@context: Help text">
-          Read the{" "}
-          <a href="/docs" class="underline">
-            documentation
-          </a>
-        </Trans>
-      </p>
-    </div>
-  );
-}
-
-// Route handler: wrap in I18nProvider
-dashRoute.get("/", async (c) => {
-  const posts = await c.var.services.posts.list();
-
-  return c.html(
-    <I18nProvider c={c}>
-      <DashboardContent postCount={posts.length} />
-    </I18nProvider>,
-  );
-});
-```
-
----
-
-## 🆚 Comparison: Before vs Now
-
-### Before (Complex - prop drilling)
-
-```tsx
-import { getI18n } from "@/i18n";
-
-dashRoute.get("/", async (c) => {
-  const i18n = getI18n(c);
-
-  return c.html(
-    <Layout title={i18n._({ message: "Dashboard", comment: "@context: ..." })}>
-      <MyComponent c={c} /> {/* Need to pass c prop */}
-    </Layout>,
-  );
-});
-
-function MyComponent({ c }: { c: Context }) {
-  const i18n = getI18n(c);
-  return <h1>{i18n._({ message: "Hello", comment: "@context: ..." })}</h1>;
-}
-```
-
-### Now (Clean - no prop drilling)
-
-```tsx
-import { I18nProvider, useLingui } from "@/i18n";
-
-dashRoute.get("/", async (c) => {
-  return c.html(
-    <I18nProvider c={c}>
-      <Layout>
-        <MyComponent /> {/* No need to pass c prop */}
-      </Layout>
-    </I18nProvider>,
-  );
-});
-
-function MyComponent() {
-  const { t } = useLingui(); // Like React hook
-  return <h1>{t({ message: "Hello", comment: "@context: ..." })}</h1>;
-}
-```
-
----
-
-## ⚠️ Important Notes
-
-### 1. **Always include `comment` field**
-
-```tsx
-// ✅ Correct - comment is crucial for AI translation
-const { t } = useLingui();
-t({ message: "Dashboard", comment: "@context: Page title" });
-
-// ❌ Wrong - missing comment reduces translation quality
-t({ message: "Dashboard" });
-```
-
-### 2. **I18nProvider must wrap your app**
-
-```tsx
-// ✅ Correct - wrap in I18nProvider
-c.html(
-  <I18nProvider c={c}>
-    <App />
-  </I18nProvider>,
-);
-
-// ❌ Wrong - useLingui() will throw error
-c.html(<App />); // useLingui() inside App won't find i18n context
-```
-
-### 3. **useLingui() only works inside components**
-
-```tsx
-// ✅ Correct - inside JSX component
-function MyComponent() {
-  const { t } = useLingui();
-  return <div>{t({ message: "Hello", comment: "@context: ..." })}</div>;
-}
-
-// ❌ Wrong - in route handler (outside I18nProvider)
-dashRoute.get("/", async (c) => {
-  const { t } = useLingui();  // Error: not inside I18nProvider
-  ...
-});
-```
-
-### 4. **Variables go in second parameter**
-
-```tsx
-const { t } = useLingui();
-
-// ✅ Correct - values as second parameter
-t(
-  { message: "Hello {name}", comment: "@context: Greeting" },
-  { name: "Alice" },
-);
-
-// ❌ Wrong - values inside first parameter (not supported)
-t({
-  message: "Hello {name}",
-  comment: "@context: Greeting",
-  values: { name: "Alice" },
-});
-```
-
----
-
-## 🎯 Best Practices
-
-1. **Route handler**: Wrap app in `<I18nProvider c={c}>`
-2. **Inside components**: Use `useLingui()` hook to get `t()` function
-3. **Translation calls**: `t({ message: "...", comment: "@context: ..." })`
-4. **With embedded JSX**: Use `<Trans>` component
-5. **Always include `comment`**: Helps AI understand context for better translations
-
----
-
-## 📚 API Reference
-
-### `I18nProvider`
-
-Provides i18n context to all child components. Must wrap your app in route handlers.
-
-```tsx
-interface I18nProviderProps {
-  c: Context; // Hono context
-  children: JSX.Element;
-}
-
-// Usage
-<I18nProvider c={c}>
-  <YourApp />
-</I18nProvider>;
-```
-
-### `useLingui()`
-
-Hook to access i18n functionality inside components. Must be used within `I18nProvider`.
-
-```tsx
-function useLingui(): {
-  i18n: I18n; // Lingui i18n instance
-  t: (descriptor: MessageDescriptor, values?: Record<string, any>) => string;
-  _: (descriptor: MessageDescriptor, values?: Record<string, any>) => string;
-};
-
-// Usage
-function MyComponent() {
-  const { t } = useLingui();
-  return <h1>{t({ message: "Hello", comment: "@context: Greeting" })}</h1>;
-}
-```
-
-**Note**: `t()` and `_()` are equivalent - use whichever you prefer.
-
-### `Trans`
-
-Component for translations with embedded JSX elements. Simplified implementation that renders children as-is.
-
-```tsx
-interface TransProps {
-  comment?: string; // @context comment for translators
-  id?: string; // Optional message ID
-  children: JSX.Element; // JSX content with embedded elements
-}
-
-// Usage
-<Trans comment="@context: Help text">
-  Read the <a href="/docs">documentation</a>
-</Trans>;
-```
-
-**Note**: This is a simplified implementation. For complex translations with dynamic content, use `t()` with placeholders instead.
-
----
-
-## 🔧 How It Works
-
-1. **I18nProvider** sets the global i18n instance during rendering
-2. **useLingui()** reads the current i18n instance from global state
-3. **Single-pass rendering**: Each request renders only once, making global state safe
-4. **Concurrency-safe**: Each request creates a new i18n instance, preventing race conditions
-
-This implementation mimics React's Context API but is optimized for Hono JSX SSR scenarios.
-
-### Why Global State is Safe
-
-Unlike React (client-side with multiple re-renders), Hono JSX renders once per request on the server:
-
-- Request arrives → I18nProvider sets global i18n → Components render → Response sent
-- Next request → New i18n instance → Components render → Response sent
-
-Since rendering is synchronous and single-pass, there's no risk of concurrent requests interfering with each other.