@tinacms/cli 0.0.0-e88638d-20250922015536 → 0.0.0-e97cc34-20260505010028

package/README.md

@@ -1,4 +1,4 @@
-The _TinaCloud CLI_ can be used to set up your project with TinaCloud configuration, and run a local version of the TinaCloud content-api (using your file system's content). For a real-world example of how this is being used checkout the [TinaCloud Starter](https://github.com/tinacms/tina-cloud-starter).
+The _TinaCloud CLI_ can be used to set up your project with TinaCloud configuration, and run a local version of the TinaCloud content-api (using your file system's content). For a real-world example of how this is being used checkout the [TinaCloud Starter](https://github.com/tinacms/tina-nextjs-starter).
 
 ## Installation
 
@@ -24,7 +24,7 @@ Usage: @tinacms/cli command [options]
 Options:
   -V, --version             output the version number
   -h, --help                display help for command
-  -v, --verbose             increase verbosity of console output   
+  -v, --verbose             increase verbosity of console output
 
 Commands:
   server:start [options]    Start Filesystem Graphql Server
@@ -32,11 +32,31 @@ Commands:
   schema:types [options]    Generate a GraphQL query for your site's schema, (and optionally Typescript types)
   init [options]            Add TinaCloud to an existing project
   audit [options]           Audit your schema and the files to check for errors
+  doctor [options]          Check direct TinaCMS dependencies against npm latest
   help [command]            display help for command
 ```
 
 [See our docs](https://tina.io/docs/cli-overview/) for more information about the commands.
 
+### `doctor`
+
+Use `tinacms doctor` to check whether the Tina packages installed in your
+project are current against the npm `latest` dist-tag.
+
+The command reads your `package.json`, resolves installed versions from
+`node_modules` or the project lockfile, filters to Tina package names
+(`tinacms`, `@tinacms/*`, `tinacms-*`, `next-tinacms-*`, and
+`create-tina-app`), then prints the installed version next to the latest
+published version.
+
+```bash
+pnpm tinacms doctor
+```
+
+Use `--json` for machine-readable output. The command exits with code `1` if a
+Tina package is outdated or if a package version cannot be checked, which makes
+it suitable for CI.
+
 ## Getting started
 
 The simplest way to get started is to add a `.tina/schema.ts` file
@@ -137,7 +157,7 @@ The top-level key in the schema is an array of _collections_, a `collection` inf
 
 ### `templates`
 
-Templates are responsible for defining the shape of your content, you'll see in the schema for [the starter](https://github.com/tinacms/tina-cloud-starter) that we use `templates` for `collections` as well as `blocks`. One important thing to note is that since a `collection` can have multiple `templates`, each file in your collection must store a `_template` key in it's frontmatter:
+Templates are responsible for defining the shape of your content, you'll see in the schema for [the starter](https://github.com/tinacms/tina-nextjs-starter) that we use `templates` for `collections` as well as `blocks`. One important thing to note is that since a `collection` can have multiple `templates`, each file in your collection must store a `_template` key in it's frontmatter:
 
 ```markdown
 ---
@@ -151,7 +171,7 @@ When you use Tina's GraphQL forms, we know about all of the relationships in you
 
 ### `fields`
 
-For the most part, you can think of `fields` as the backend equivalent to [Tina field plugins](https://tina.io/docs/plugins/fields/). You might notice that we're defining a `type` on each field, rather than a `component`. This is because the backend isn't concerned with `component`s, only the shape of your content. By default we use the built-in Tina fields, to customize your `component` read the [field customization](https://tina.io/docs/tina-cloud/client/#field-customization) instructions.
+For the most part, you can think of `fields` as the backend equivalent to [Tina field plugins](https://tina.io/docs/plugins/fields/). You might notice that we're defining a `type` on each field, rather than a `component`. This is because the backend isn't concerned with `component`s, only the shape of your content. By default we use the built-in Tina fields, to customize your `component` read the [field customization](https://tina.io/docs/tinacloud/client/#field-customization) instructions.
 
 #### `reference` & `reference-list`
 
@@ -229,7 +249,7 @@ getPostsDocument(relativePath: "voteForPedro.md") {
 }
 ```
 
-To learn how to work with this data on a Tina-enabled site, check out the [client documentation](https://tina.io/docs/tina-cloud/client/)
+To learn how to work with this data on a Tina-enabled site, check out the [client documentation](https://tina.io/docs/tinacloud/client/)
 
 > This API is currently somewhat limited. Specifically there's no support for filtering and sorting "list" queries. We have plans to tackle that in upcoming cycles
 

package/bin/tinacms

@@ -1,13 +1,19 @@
 #!/usr/bin/env node
 
-const version = process.version.slice(1)
-const [major, minor] = version.split('.')
+const version = process.version.slice(1);
+const [major, minor] = version.split('.');
 if (major < 14 || (major == 14 && minor < 18)) {
   console.error(
     'ERROR: Node.js version lower than 14.18 is not supported in tinacms, please update to the latest LTS version. See https://nodejs.org/en/download/ for more details'
-  )
+  );
 } else {
-  const cli = require('../dist/index.js')
-  const [node, app, ...args] = process.argv
-  cli.default.runExit(args)
+  const [node, app, ...args] = process.argv;
+  import('../dist/index.js')
+    .then((cli) => {
+      cli.default.runExit(args);
+    })
+    .catch((err) => {
+      console.error('Failed to load CLI:', err);
+      process.exit(1);
+    });
 }

package/dist/cmds/forestry-migrate/util/index.d.ts

@@ -59,7 +59,6 @@ declare const forestryFieldWithoutField: z.ZodObject<{
         };
     }>>;
 }, "strip", z.ZodTypeAny, {
-    type?: "number" | "boolean" | "file" | "text" | "color" | "include" | "list" | "datetime" | "select" | "image_gallery" | "textarea" | "tag_list" | "field_group" | "field_group_list" | "blocks";
     default?: any;
     name?: string;
     config?: {
@@ -76,10 +75,10 @@ declare const forestryFieldWithoutField: z.ZodObject<{
         };
     };
     label?: string;
+    type?: "number" | "boolean" | "text" | "color" | "file" | "include" | "list" | "datetime" | "select" | "image_gallery" | "textarea" | "tag_list" | "field_group" | "field_group_list" | "blocks";
     template?: string;
     template_types?: string[];
 }, {
-    type?: "number" | "boolean" | "file" | "text" | "color" | "include" | "list" | "datetime" | "select" | "image_gallery" | "textarea" | "tag_list" | "field_group" | "field_group_list" | "blocks";
     default?: any;
     name?: string;
     config?: {
@@ -96,6 +95,7 @@ declare const forestryFieldWithoutField: z.ZodObject<{
         };
     };
     label?: string;
+    type?: "number" | "boolean" | "text" | "color" | "file" | "include" | "list" | "datetime" | "select" | "image_gallery" | "textarea" | "tag_list" | "field_group" | "field_group_list" | "blocks";
     template?: string;
     template_types?: string[];
 }>;
@@ -149,12 +149,12 @@ export declare const parseSections: ({ val }: {
     val: unknown;
 }) => {
     sections?: {
-        exclude?: string;
-        type?: "heading" | "document" | "directory" | "jekyll-pages" | "jekyll-posts";
         match?: string;
         templates?: string[];
         label?: string;
         path?: string;
+        type?: "heading" | "document" | "directory" | "jekyll-pages" | "jekyll-posts";
+        exclude?: string;
         create?: "none" | "all" | "documents";
         new_doc_ext?: string;
         read_only?: boolean;