@tinacms/cli 2.2.4 → 2.2.6

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -32,11 +32,31 @@ Commands:
32
32
  schema:types [options] Generate a GraphQL query for your site's schema, (and optionally Typescript types)
33
33
  init [options] Add TinaCloud to an existing project
34
34
  audit [options] Audit your schema and the files to check for errors
35
+ doctor [options] Check direct TinaCMS dependencies against npm latest
35
36
  help [command] display help for command
36
37
  ```
37
38
 
38
39
  [See our docs](https://tina.io/docs/cli-overview/) for more information about the commands.
39
40
 
41
+ ### `doctor`
42
+
43
+ Use `tinacms doctor` to check whether the Tina packages installed in your
44
+ project are current against the npm `latest` dist-tag.
45
+
46
+ The command reads your `package.json`, resolves installed versions from
47
+ `node_modules` or the project lockfile, filters to Tina package names
48
+ (`tinacms`, `@tinacms/*`, `tinacms-*`, `next-tinacms-*`, and
49
+ `create-tina-app`), then prints the installed version next to the latest
50
+ published version.
51
+
52
+ ```bash
53
+ pnpm tinacms doctor
54
+ ```
55
+
56
+ Use `--json` for machine-readable output. The command exits with code `1` if a
57
+ Tina package is outdated or if a package version cannot be checked, which makes
58
+ it suitable for CI.
59
+
40
60
  ## Getting started
41
61
 
42
62
  The simplest way to get started is to add a `.tina/schema.ts` file