create-meith 0.25.0 → 0.26.0

package/dist/bin.mjs

@@ -53,7 +53,7 @@ var AT_ROOT_IGNORES = `# What \`forum-web ${AT_ROOT_FLAG}\` writes into this dir
 # alone by the build and still never committed, so it works locally and is
 # simply absent from the deploy, which builds from what git has. Extend the
 # board with a plugin or a theme instead \u2014 the forum loads those from
-# community.config.ts, and they are yours to commit. forum-web prints a
+# meith.config.ts, and they are yours to commit. forum-web prints a
 # warning naming any file of yours it finds there.
 #
 # For the rest, a build refuses rather than overwriting a file it did not
@@ -425,7 +425,7 @@ save-exact=true
 `
   );
   files.set(
-    "community.config.ts",
+    "meith.config.ts",
     `/**
  * The board's build-time registry.
  *
@@ -436,7 +436,7 @@ save-exact=true
  * not there at all.
  *
  * Adding a theme is: \`npm install\` it, add a line here, redeploy. Adding a
- * plugin is the same, through board.plugins.json and community.plugins.ts \u2014
+ * plugin is the same, through board.plugins.json and meith.plugins.ts \u2014
  * see docs/customization/plugins.md.
  */
 import { defineForumConfig } from '@meith/web/config'
@@ -448,7 +448,7 @@ import {
   LIGHT_TOKENS,
 } from '@meith/theme-default'
 
-import { INSTALLED_PLUGINS } from './community.plugins'
+import { INSTALLED_PLUGINS } from './meith.plugins'
 
 export default defineForumConfig({
   themes: {
@@ -470,7 +470,7 @@ export default defineForumConfig({
   files.set("board.plugins.json", `${JSON.stringify({ plugins: [] }, null, 2)}
 `);
   files.set(
-    "community.plugins.ts",
+    "meith.plugins.ts",
     `/**
  * The board's installed-plugin list.
  *
@@ -560,7 +560,7 @@ FROM ghcr.io/meith-dev/meith-base:\${MEITH_VERSION} AS deps
 WORKDIR /board
 
 # This board's own manifest, cached independently of its source \u2014 editing
-# community.config.ts should not re-run npm install. The base image above
+# meith.config.ts should not re-run npm install. The base image above
 # already carries node_modules for @meith/web, @meith/cli and
 # @meith/theme-default at this exact version, so installing this file on top
 # of it only fetches what changed: a plugin newly added to \`dependencies\`,
@@ -952,7 +952,7 @@ echo "<password>" | npm run community -- user:create --username <name> --email <
 
 ## Configuring
 
-- **\`community.config.ts\`** \u2014 installed themes and plugins. Everything installable
+- **\`meith.config.ts\`** \u2014 installed themes and plugins. Everything installable
   is named here so the bundler can see it; nothing is found by scanning a
   directory at runtime.
 - **\`/admin\`** \u2014 settings, forums, groups, members, themes, maintenance. An
@@ -1607,7 +1607,7 @@ Scaffold a board next to this directory if you do not have one
 npm installs a local directory as a symlink, so edits here are picked up by
 the board's next build without reinstalling.
 
-Register the plugin in the board's \`community.plugins.ts\` \u2014 the comment at
+Register the plugin in the board's \`meith.plugins.ts\` \u2014 the comment at
 the top of that file shows the shape:
 
     import { messages as ${camel}Messages, plugin as ${camel}Plugin } from '${name}'
@@ -1663,7 +1663,7 @@ Scaffold a board next to this directory if you do not have one
 npm installs a local directory as a symlink, so edits here are picked up by
 the board's next build without reinstalling.
 
-Register the theme in the board's \`community.config.ts\`, beside the
+Register the theme in the board's \`meith.config.ts\`, beside the
 default entry:
 
     import { defaultMessages } from '@meith/theme-default'
@@ -1890,7 +1890,7 @@ async function run(argv, version) {
 }
 
 // src/bin.ts
-var result = await run(process.argv.slice(2), "0.25.0");
+var result = await run(process.argv.slice(2), "0.26.0");
 for (const line of result.lines) {
   if (result.code === 0) console.log(line);
   else console.error(line);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "create-meith",
-  "version": "0.25.0",
+  "version": "0.26.0",
   "description": "Scaffold a Meith board, plugin or theme — npx create-meith <name> writes a deployable board workspace; --plugin and --theme write extension workspaces built on the published kits.",
   "license": "MIT",
   "repository": {

package/src/bin.ts

@@ -1,7 +1,7 @@
 #!/usr/bin/env node
 import { run } from './cli'
 
-const result = await run(process.argv.slice(2), '0.25.0')
+const result = await run(process.argv.slice(2), '0.26.0')
 for (const line of result.lines) {
   if (result.code === 0) console.log(line)
   else console.error(line)

package/src/scaffold-extension.ts

@@ -192,7 +192,7 @@ Scaffold a board next to this directory if you do not have one
 npm installs a local directory as a symlink, so edits here are picked up by
 the board's next build without reinstalling.
 
-Register the plugin in the board's \`community.plugins.ts\` — the comment at
+Register the plugin in the board's \`meith.plugins.ts\` — the comment at
 the top of that file shows the shape:
 
     import { messages as ${camel}Messages, plugin as ${camel}Plugin } from '${name}'
@@ -249,7 +249,7 @@ Scaffold a board next to this directory if you do not have one
 npm installs a local directory as a symlink, so edits here are picked up by
 the board's next build without reinstalling.
 
-Register the theme in the board's \`community.config.ts\`, beside the
+Register the theme in the board's \`meith.config.ts\`, beside the
 default entry:
 
     import { defaultMessages } from '@meith/theme-default'

package/src/scaffold.ts

@@ -65,7 +65,7 @@ const AT_ROOT_IGNORES = `# What \`forum-web ${AT_ROOT_FLAG}\` writes into this d
 # alone by the build and still never committed, so it works locally and is
 # simply absent from the deploy, which builds from what git has. Extend the
 # board with a plugin or a theme instead — the forum loads those from
-# community.config.ts, and they are yours to commit. forum-web prints a
+# meith.config.ts, and they are yours to commit. forum-web prints a
 # warning naming any file of yours it finds there.
 #
 # For the rest, a build refuses rather than overwriting a file it did not
@@ -460,7 +460,7 @@ save-exact=true
   )
 
   files.set(
-    'community.config.ts',
+    'meith.config.ts',
     `/**
  * The board's build-time registry.
  *
@@ -471,7 +471,7 @@ save-exact=true
  * not there at all.
  *
  * Adding a theme is: \`npm install\` it, add a line here, redeploy. Adding a
- * plugin is the same, through board.plugins.json and community.plugins.ts —
+ * plugin is the same, through board.plugins.json and meith.plugins.ts —
  * see docs/customization/plugins.md.
  */
 import { defineForumConfig } from '@meith/web/config'
@@ -483,7 +483,7 @@ import {
   LIGHT_TOKENS,
 } from '@meith/theme-default'
 
-import { INSTALLED_PLUGINS } from './community.plugins'
+import { INSTALLED_PLUGINS } from './meith.plugins'
 
 export default defineForumConfig({
   themes: {
@@ -506,7 +506,7 @@ export default defineForumConfig({
   files.set('board.plugins.json', `${JSON.stringify({ plugins: [] }, null, 2)}\n`)
 
   files.set(
-    'community.plugins.ts',
+    'meith.plugins.ts',
     `/**
  * The board's installed-plugin list.
  *
@@ -600,7 +600,7 @@ FROM ghcr.io/meith-dev/meith-base:\${MEITH_VERSION} AS deps
 WORKDIR /board
 
 # This board's own manifest, cached independently of its source — editing
-# community.config.ts should not re-run npm install. The base image above
+# meith.config.ts should not re-run npm install. The base image above
 # already carries node_modules for @meith/web, @meith/cli and
 # @meith/theme-default at this exact version, so installing this file on top
 # of it only fetches what changed: a plugin newly added to \`dependencies\`,
@@ -998,7 +998,7 @@ echo "<password>" | npm run community -- user:create --username <name> --email <
 
 ## Configuring
 
-- **\`community.config.ts\`** — installed themes and plugins. Everything installable
+- **\`meith.config.ts\`** — installed themes and plugins. Everything installable
   is named here so the bundler can see it; nothing is found by scanning a
   directory at runtime.
 - **\`/admin\`** — settings, forums, groups, members, themes, maintenance. An