@plume-press/cli 0.4.0 → 0.6.0
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 +1 -1
- package/dist/cli.mjs +234 -458
- package/dist/local.mjs +15 -39
- package/dist/schema.d.ts +1 -7
- package/dist/schema.mjs +6 -19
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,3 +1,3 @@
|
|
|
1
1
|
# @plume-press/cli
|
|
2
2
|
|
|
3
|
-
Use Node 22.13 or newer. Run `npx plume init` in your website directory: it creates `plume.schema.ts` and a local CMS, and adds the Plume SDK to package.json. Run `npx plume local schema` after editing collection definitions. Import `defineSchema` from `@plume-press/cli/schema` in `plume.schema.ts`. Make your build script `plume build -- <your build command>`: it checks the committed `plume.lock` with Plume (`PLUME_ENDPOINT`, default `https://app.plume.press`; no token
|
|
3
|
+
Use Node 22.13 or newer. Run `npx plume init` in your website directory: it creates `plume.schema.ts` and a local CMS, and adds the Plume SDK to package.json. Run `npx plume local schema` after editing collection definitions. Import `defineSchema` from `@plume-press/cli/schema` in `plume.schema.ts`. Make your build script `plume build -- <your build command>`: it checks the committed `plume.lock` with Plume (`PLUME_ENDPOINT`, default `https://app.plume.press`; no token; the same command builds production and your host's preview deployments) and writes `.plume/binding.json` for the SDK before your build runs. Run `npx plume --help` for every command.
|