rimecms 0.31.5 → 0.32.0

package/dist/core/dev/cli/init/templates.js

@@ -1,116 +0,0 @@
-import { randomId } from '../../../../util/random.js';
-import { existsSync, mkdirSync, readFileSync, writeFileSync } from 'node:fs';
-import path from 'node:path';
-import { CONFIG_DIR, GENERATED_DIR, PANEL_ROUTE, configImportPaths } from '../../constants.js';
-const PACKAGE = 'rimecms';
-export const env = () => `BETTER_AUTH_SECRET=${randomId(32)}
-PUBLIC_RIME_URL=http://localhost:5173
-RIME_CONFIG_DIR=${CONFIG_DIR}
-
-# Panel URL segment (e.g. /panel/...). Change it to hide the panel from
-# automated CMS-admin scanners — requests to the old segment 404 instead of
-# revealing a login page. Run 'rime generate' (or restart 'rime dev') after
-# changing this — the dev server only regenerates routes when it detects a
-# change under RIME_CONFIG_DIR, not on every restart.
-RIME_PANEL_ROUTE=${PANEL_ROUTE}
-
-# RIME_CACHE_ENABLED=false
-# RIME_SMTP_USER=user@mail.com
-# RIME_SMTP_PASSWORD=supersecret
-# RIME_SMTP_HOST=smtphost.com
-# RIME_SMTP_PORT=465
-
-RIME_CACHE_ENABLED=false
-RIME_LOG_LEVEL=TRACE
-RIME_LOG_TO_FILE=true
-RIME_LOG_TO_FILE_MAX_DAYS=1
-`;
-export const defaultConfig = (name) => `
-import { Collection, rime } from '$rime/config';
-import { text } from '${PACKAGE}/fields';
-import { adapterSqlite } from '${PACKAGE}/adapter-sqlite';
-
-const Pages = Collection.create('pages', {
-	fields: [text('title').isTitle()]
-});
-
-const Medias = Collection.create('medias', {
-  upload: true,
-	fields: [
-    text('alt').required(),
-  ]
-});
-
-export default rime({
-  $adapter: adapterSqlite('${name}.sqlite'),
-  collections: [Pages, Medias]
-});
-`;
-export const drizzleConfig = (name) => `
-import { defineConfig, type Config } from 'drizzle-kit';
-
-export const config: Config = {
-  schema: './${GENERATED_DIR}/schema.server.ts',
-  out: './db',
-  strict: false,
-  dialect: 'sqlite',
-  dbCredentials: {
-    url: './db/${name}.sqlite'
-  }
-};
-
-export default defineConfig(config);
-`;
-// Regenerated fresh by rime init every time (setHooks() only skips if the file already
-// exists, and `rime clear`/useConfig.js delete it first) — safe to make mode-aware.
-const HOOKS_DIR = path.resolve(process.cwd(), 'src');
-export const hooks = () => `import { sequence } from '@sveltejs/kit/hooks';
-import { handlers } from '${PACKAGE}/server';
-import config from '${configImportPaths(HOOKS_DIR).server}';
-
-export const handle = sequence(...(await handlers(config)));
-`;
-const HOOKS_CONFIG_IMPORT_LINE_REGEX = /^import config from ['"][^'"]*['"];\s*$/m;
-/** Writes src/hooks.server.ts if missing. If it already exists, patches only the config
- * import line if it's stale (e.g. after RIME_CONFIG_DIR changes the import path) — the rest
- * of the file may carry real customizations (e.g. an appended handler), so this never
- * touches anything else. Called both at `rime init` and whenever the dev server detects a
- * config change, so the import path never goes stale between the two. Returns whether it
- * wrote anything. */
-export function regenerateHooks(root = process.cwd()) {
-    const hooksPath = path.join(root, 'src', 'hooks.server.ts');
-    const srcDir = path.join(root, 'src');
-    if (!existsSync(hooksPath)) {
-        if (!existsSync(srcDir)) {
-            mkdirSync(srcDir, { recursive: true });
-        }
-        writeFileSync(hooksPath, hooks(), 'utf-8');
-        return true;
-    }
-    const expectedImportLine = `import config from '${configImportPaths(HOOKS_DIR).server}';`;
-    const content = readFileSync(hooksPath, 'utf-8');
-    if (HOOKS_CONFIG_IMPORT_LINE_REGEX.test(content) && !content.includes(expectedImportLine)) {
-        writeFileSync(hooksPath, content.replace(HOOKS_CONFIG_IMPORT_LINE_REGEX, expectedImportLine));
-        return true;
-    }
-    return false;
-}
-const DRIZZLE_SCHEMA_LINE_REGEX = /^\s*schema:\s*['"][^'"]*['"],?\s*$/m;
-/** Patches drizzle.config.ts's schema path line if it's stale (e.g. after RIME_CONFIG_DIR
- * changes) — only that one line, since the rest of the file may carry real customizations
- * (verbose, custom fields, etc.). Must run before generateSchema()'s own drizzle-kit
- * generate/migrate shell-out, which reads this file from disk. No-op if the file doesn't
- * exist — creating it from scratch needs a project name, which is `rime init`'s job
- * (setDrizzle() in init/index.server.ts). Returns whether it patched anything. */
-export function regenerateDrizzleConfig(root = process.cwd()) {
-    const drizzleConfigPath = path.join(root, 'drizzle.config.ts');
-    if (!existsSync(drizzleConfigPath))
-        return false;
-    const expectedSchemaLine = `  schema: './${GENERATED_DIR}/schema.server.ts',`;
-    const content = readFileSync(drizzleConfigPath, 'utf-8');
-    if (DRIZZLE_SCHEMA_LINE_REGEX.test(content) && !content.includes(expectedSchemaLine)) {
-        writeFileSync(drizzleConfigPath, content.replace(DRIZZLE_SCHEMA_LINE_REGEX, expectedSchemaLine));
-        return true;
-    }
-    return false;
-}

package/dist/core/dev/cli/util/log.server.d.ts

@@ -1 +0,0 @@
-export declare const dim: (text: string) => void;

package/dist/core/dev/cli/util/log.server.js

@@ -1,4 +0,0 @@
-import chalk from 'chalk';
-export const dim = (text) => {
-    console.log(chalk.dim(text));
-};

package/dist/core/dev/constants.d.ts

@@ -1,34 +0,0 @@
-export declare const CONFIG_DIR: string;
-export declare const GENERATED_DIR: string;
-export declare const INPUT_DIR: string;
-export declare const OUTPUT_DIR: string;
-/** The panel's URL segment (e.g. "panel" -> /panel/...). Kept as a bare segment, never a
- * PUBLIC_-prefixed env var: SvelteKit ships every PUBLIC_ value into the JS bundle of every
- * page (including the public site), which would defeat the point of letting an operator hide
- * this path from automated CMS-admin scanners. */
-export declare const PANEL_ROUTE: string;
-/** Turns an absolute path into an import specifier relative to `fromDir`, always prefixed
- * with `./` or `../` so it never gets mistaken for a bare package specifier. */
-export declare function relativeImportSpecifier(fromDir: string, toAbsolutePath: string): string;
-export declare function generatedConfigServerPath(): string;
-/** Where the panel/live route templates (common.server.ts) and the generated hooks.server.ts
- * should import the client/server config from — a relative import specifier computed from
- * `fromDir` (the absolute directory of the file doing the importing), so it resolves whether
- * GENERATED_DIR lives under src/lib or elsewhere. One source of truth instead of hardcoding the
- * path (or relying on the $lib alias, which only ever points at src/lib) at each call site. */
-export declare function configImportPaths(fromDir: string): {
-    client: string;
-    server: string;
-};
-/** Same idea as configImportPaths — one source of truth for where the generated schema
- * lives instead of hardcoding the path at each call site. */
-export declare function schemaPath(projectRoot?: string): string;
-/**
- * True when `metaUrl` (pass the caller's own `import.meta.url` — this can't be one shared
- * value, it depends on which file is asking) is running from inside an installed `rimecms`
- * package (node_modules/rimecms/...), false when running from rime's own repo. Deliberately
- * filesystem-based rather than an env var: a shell dotenv plugin auto-loading this repo's own
- * .env (which used to set IS_RIME_REPO=true) into every child process — including an unrelated
- * consumer app's dev server — made that value unreliable; this can't leak the same way.
- */
-export declare function isInstalledDependency(metaUrl: string): boolean;

package/dist/core/dev/constants.js

@@ -1,76 +0,0 @@
-import dotenv from 'dotenv';
-import path from 'node:path';
-import { isValidSlug } from '../../util/string.js';
-// Must run before RIME_CONFIG_DIR is read below. ES import hoisting evaluates this module's
-// top-level code before any *importing* file's own top-level statements — including a
-// dotenv.config() call there — so loading .env here, first, is the only way every entry point
-// (CLI, dev-server, drizzle.config.ts, etc.) reliably sees it. override:true so .env is the
-// explicit source of truth, not whatever a shell plugin (autoenv, direnv, ...) already exported
-// from some other project's .env. The only dotenv.config() call in the codebase — a second one
-// elsewhere would race this one.
-dotenv.config({ override: true });
-const root = process.cwd();
-const SRC_ROOT = path.resolve(root, 'src');
-export const CONFIG_DIR = process.env.RIME_CONFIG_DIR || 'src/+rime';
-export const GENERATED_DIR = `${CONFIG_DIR}.generated`;
-export const INPUT_DIR = path.basename(CONFIG_DIR);
-export const OUTPUT_DIR = `${INPUT_DIR}.generated`;
-/** The panel's URL segment (e.g. "panel" -> /panel/...). Kept as a bare segment, never a
- * PUBLIC_-prefixed env var: SvelteKit ships every PUBLIC_ value into the JS bundle of every
- * page (including the public site), which would defeat the point of letting an operator hide
- * this path from automated CMS-admin scanners. */
-export const PANEL_ROUTE = (process.env.RIME_PANEL_ROUTE || 'panel').replace(/^\/+|\/+$/g, '');
-if (!isValidSlug(PANEL_ROUTE)) {
-    throw new Error(`RIME_PANEL_ROUTE must be a single URL segment (letters, numbers, "_"/"-", starting with a letter) — got "${PANEL_ROUTE}"`);
-}
-const RESERVED_DIRS = new Set(['lib', 'routes', 'static', 'params'].map((d) => path.resolve(SRC_ROOT, d)));
-for (const dir of [CONFIG_DIR, GENERATED_DIR]) {
-    const resolved = path.resolve(root, dir);
-    if (resolved === SRC_ROOT || !resolved.startsWith(SRC_ROOT + path.sep)) {
-        throw new Error(`RIME_CONFIG_DIR must resolve to a subdirectory of ${SRC_ROOT} (got "${dir}")`);
-    }
-    if (RESERVED_DIRS.has(resolved)) {
-        throw new Error(`RIME_CONFIG_DIR must not be src/lib, src/routes, src/static, or src/params (got "${dir}")`);
-    }
-}
-/** Turns an absolute path into an import specifier relative to `fromDir`, always prefixed
- * with `./` or `../` so it never gets mistaken for a bare package specifier. */
-export function relativeImportSpecifier(fromDir, toAbsolutePath) {
-    const rel = path.relative(fromDir, toAbsolutePath).split(path.sep).join('/');
-    return rel.startsWith('.') ? rel : `./${rel}`;
-}
-/** Root-relative filesystem path (posix-style) to a file inside the generated config dir —
- * for Vite's ssrLoadModule, which wants a real file path, not an import specifier. */
-function generatedFilePath(file) {
-    return path.relative(root, path.resolve(root, GENERATED_DIR, file)).split(path.sep).join('/');
-}
-export function generatedConfigServerPath() {
-    return generatedFilePath('rime.config.server.ts');
-}
-/** Where the panel/live route templates (common.server.ts) and the generated hooks.server.ts
- * should import the client/server config from — a relative import specifier computed from
- * `fromDir` (the absolute directory of the file doing the importing), so it resolves whether
- * GENERATED_DIR lives under src/lib or elsewhere. One source of truth instead of hardcoding the
- * path (or relying on the $lib alias, which only ever points at src/lib) at each call site. */
-export function configImportPaths(fromDir) {
-    return {
-        client: relativeImportSpecifier(fromDir, path.resolve(root, GENERATED_DIR, 'rime.config.js')),
-        server: relativeImportSpecifier(fromDir, path.resolve(root, GENERATED_DIR, 'rime.config.server.js'))
-    };
-}
-/** Same idea as configImportPaths — one source of truth for where the generated schema
- * lives instead of hardcoding the path at each call site. */
-export function schemaPath(projectRoot = process.cwd()) {
-    return path.resolve(projectRoot, GENERATED_DIR, 'schema.server.ts');
-}
-/**
- * True when `metaUrl` (pass the caller's own `import.meta.url` — this can't be one shared
- * value, it depends on which file is asking) is running from inside an installed `rimecms`
- * package (node_modules/rimecms/...), false when running from rime's own repo. Deliberately
- * filesystem-based rather than an env var: a shell dotenv plugin auto-loading this repo's own
- * .env (which used to set IS_RIME_REPO=true) into every child process — including an unrelated
- * consumer app's dev server — made that value unreliable; this can't leak the same way.
- */
-export function isInstalledDependency(metaUrl) {
-    return metaUrl.includes('/node_modules/rimecms/');
-}

package/dist/core/dev/generate/routes/common.server.d.ts

@@ -1,17 +0,0 @@
-import type { Routes } from './util.server.js';
-/**
- * Param matchers backing [slug=collection]/[slug=area] — bake in the actual
- * configured slug list at generation time so they stay isomorphic (no
- * server-only config import; SvelteKit resolves matchers on the client too
- * for client-side navigation), same approach as this repo's own hand-written
- * src/params/news.ts, lang.ts.
- * src/params/collection.ts, src/params/area.ts
- */
-declare const paramMatcher: (slugs: string[]) => string;
-/**
- * Custom route template generator
- * Used for generating custom routes
- */
-declare const customRoute: (config: any) => string;
-export declare const commonRoutes: Routes;
-export { customRoute, paramMatcher };