@tinacms/cli 2.3.0 → 2.4.0

package/dist/next/build-database-esbuild-config.d.ts

@@ -0,0 +1,38 @@
+import type { BuildOptions, Loader } from 'esbuild';
+/**
+ * Construct the esbuild options used by `loadDatabaseFile()` to bundle a
+ * user's `tina/database.ts`.
+ *
+ * Extracted from `config-manager.ts` so the externalize / output-path
+ * contract — both critical for the ESM native-module fix (#6675, #6750) —
+ * can be locked down by unit tests without spinning up the full
+ * ConfigManager (which uses `import.meta.url` at module load and isn't
+ * directly importable from Jest's CJS runtime).
+ *
+ * The contract enforced here is intentionally strict:
+ *
+ * - `external` is set to the caller-provided list (typically the curated
+ *   baseline + `build.externalDependencies`). NEVER set `packages: 'external'`
+ *   — broad-externalize would also externalize CJS UMD packages like
+ *   `sqlite-level` (v1) and `mongodb-level`, breaking user-side named imports
+ *   because Node's `cjs-module-lexer` can't reliably detect their exports.
+ *   See #6785 for the regression test that locks this down.
+ *
+ * - `outfile` is whatever the caller passes in. The caller is responsible for
+ *   constructing a path inside the project tree (typically via
+ *   `prepareCacheLocation()` from `cache-manager.ts`) so Node's runtime
+ *   resolver can walk up to the project's `node_modules` and find the
+ *   externalized packages.
+ */
+export declare const buildDatabaseEsbuildConfig: (opts: {
+    /** Path to the user's `tina/database.ts`. */
+    entryPoint: string;
+    /** Where esbuild writes the bundled `.mjs`. Must be inside the project tree. */
+    outfile: string;
+    /** Externalized package names (must include `better-sqlite3` baseline). */
+    external: string[];
+    /** Loader map shared with the rest of the CLI (asset extensions, .ts/.tsx, etc.). */
+    loader: {
+        [ext: string]: Loader;
+    };
+}) => BuildOptions;

package/dist/next/cache-manager.d.ts

@@ -0,0 +1,51 @@
+/**
+ * Per-build cache layout under `tina/__generated__/.cache/`.
+ *
+ * Each `tinacms dev` / `tinacms build` invocation creates one
+ * `<timestamp>/` subdir for esbuild output. The subdir is removed after
+ * the dynamic-import resolves; the parent is swept on next startup to
+ * mop up anything a crashed run (Ctrl+C mid-build, OOM kill, etc.) left
+ * behind.
+ */
+export type CacheLocation = {
+    /** `<project>/tina/__generated__/.cache/` — the long-lived parent. */
+    parentPath: string;
+    /** `<project>/tina/__generated__/.cache/<timestamp>/` — fresh per build. */
+    buildPath: string;
+};
+/**
+ * Build the user-facing error message thrown when the cache parent can't
+ * be written to (Docker `:ro` mount, AWS Lambda `/var/task`, sandboxed CI
+ * runner, restricted file permissions, …).
+ *
+ * Exported for testing — kept separate from {@link prepareCacheLocation}
+ * so the message contract can be locked down without spinning up a real
+ * read-only directory.
+ */
+export declare const buildReadOnlyMountErrorMessage: (cacheParentPath: string, underlyingError: NodeJS.ErrnoException) => string;
+/**
+ * Sweep stale cache residue, ensure the parent dir exists and is
+ * writable, and return the fresh per-build cache location.
+ *
+ * Throws an actionable error (built via
+ * {@link buildReadOnlyMountErrorMessage}) when the project tree can't
+ * be written to.
+ *
+ * @param generatedFolderPath The project's `tina/__generated__/` dir.
+ * @param now Override for the timestamp (tests pass a fixed value;
+ *            production passes nothing so `Date.now()` is used).
+ */
+export declare const prepareCacheLocation: (generatedFolderPath: string, now?: number) => Promise<CacheLocation>;
+/**
+ * Cleanup a per-load build subdir after its dynamic-import resolves.
+ *
+ * Removes the subdir entirely (not just the .mjs file), then attempts
+ * to reap the timestamp parent if it's now empty — the sibling load
+ * function may have already finished and removed its own subdir.
+ *
+ * `ENOTEMPTY` is the expected case for the parent reap (other content
+ * still in flight) and is safely deferred to the next startup sweep.
+ * Any other error re-throws so genuine permission / filesystem issues
+ * surface instead of being silently swallowed.
+ */
+export declare const reapBuildSubdir: (buildSubdirPath: string, buildParentPath: string) => void;

package/dist/next/commands/build-command/index.d.ts

@@ -18,6 +18,9 @@ export declare class BuildCommand extends BaseCommand {
     previewName: string;
     noClientBuildCache: boolean;
     static usage: import("clipanion").Usage;
+    private posthogClient;
+    private buildStartedAt;
+    private buildRunId;
     catch(error: any): Promise<void>;
     execute(): Promise<number | void>;
     checkClientInfo(configManager: ConfigManager, apiURL: string, previewBaseBranch?: string): Promise<{

package/dist/next/external-resolver.d.ts

@@ -0,0 +1,23 @@
+import type { Config } from '@tinacms/schema-tools';
+/**
+ * Packages always externalized when bundling `tina/database.ts`.
+ *
+ * `better-sqlite3` is a native CJS module — it ships a `.node` binary and its
+ * `bindings` dependency uses `__filename` to locate it. Both fundamentals are
+ * incompatible with ESM bundling, so it must be left as a runtime import.
+ *
+ * Users can extend this list via `build.externalDependencies` in their
+ * `tina/config.ts` when they need to externalize additional packages (e.g.
+ * a custom native adapter outside this baseline).
+ */
+export declare const EXTERNAL_BASELINE: string[];
+/**
+ * Resolve the full list of packages to externalize when bundling
+ * `tina/database.ts`. Combines the always-on baseline (which fixes native
+ * modules out of the box) with the user-provided
+ * `build.externalDependencies` extension list from their config.
+ *
+ * Order is significant: baseline first, then user list — so users can't
+ * accidentally remove an item from the baseline by listing it themselves.
+ */
+export declare const resolveDatabaseExternals: (config: Config | undefined) => string[];

package/dist/utils/fetchPostHogConfig.d.ts

@@ -0,0 +1,5 @@
+export interface PostHogConfig {
+    POSTHOG_API_KEY?: string;
+    POSTHOG_ENDPOINT?: string;
+}
+export default function fetchPostHogConfig(endpointUrl: string): Promise<PostHogConfig>;

package/dist/utils/posthog.d.ts

@@ -0,0 +1,21 @@
+import { PostHog } from 'posthog-node';
+export declare function generateSessionId(): string;
+export declare const BuildInvokeEvent = "tinacms-cli-build-invoke";
+export type BuildInvokeEventPayload = {
+    hasLocalOption: boolean;
+    hasContentLocal: boolean;
+    skipIndexing: boolean;
+    partialReindex: boolean;
+    hasPreviewName: boolean;
+    specifiesTinaGraphQLVersions?: boolean;
+    skipCloudChecks: boolean;
+    skipSearchIndex: boolean;
+};
+export declare const BuildFinishedEvent = "tinacms-cli-build-finished";
+export type BuildFinishedEventPayload = {
+    success: boolean;
+    durationMs: number;
+    errorCode?: string;
+};
+export declare function initializePostHog(configEndpoint?: string, disableGeoip?: boolean): Promise<PostHog | null>;
+export declare function postHogCapture(client: PostHog, distinctId: string, event: string, properties: Record<string, any>): void;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@tinacms/cli",
   "type": "module",
-  "version": "2.3.0",
+  "version": "2.4.0",
   "main": "dist/index.js",
   "typings": "dist/index.d.ts",
   "files": [
@@ -41,6 +41,7 @@
     "@types/progress": "^2.0.7",
     "@types/prompts": "^2.4.9",
     "jest": "^29.7.0",
+    "ts-jest": "^29.2.5",
     "@tinacms/scripts": "1.6.1"
   },
   "dependencies": {
@@ -78,6 +79,7 @@
     "memory-level": "^1.0.0",
     "minimatch": "^5.1.6",
     "normalize-path": "^3.0.0",
+    "posthog-node": "^5.17.2",
     "prettier": "^2.8.8",
     "progress": "^2.0.3",
     "prompts": "^2.4.2",
@@ -88,12 +90,12 @@
     "vite": "^4.5.9",
     "yup": "^1.6.1",
     "zod": "^3.24.2",
-    "@tinacms/graphql": "2.4.0",
-    "@tinacms/schema-tools": "2.7.4",
     "@tinacms/metrics": "2.1.0",
-    "@tinacms/search": "1.2.14",
-    "@tinacms/app": "2.4.7",
-    "tinacms": "3.8.0"
+    "@tinacms/app": "2.5.0",
+    "@tinacms/schema-tools": "2.8.0",
+    "@tinacms/graphql": "2.4.2",
+    "@tinacms/search": "1.2.16",
+    "tinacms": "3.8.2"
   },
   "publishConfig": {
     "registry": "https://registry.npmjs.org"