@3sln/create-trove 0.0.16 → 0.0.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@3sln/create-trove",
-  "version": "0.0.16",
+  "version": "0.0.18",
   "type": "module",
   "description": "Scaffold a Trove deployment — Bun, Node, or Cloudflare Workers — with the bindings, environment and secrets each one needs.",
   "repository": {

package/src/plan.js

@@ -348,7 +348,7 @@ export async function askPlan(prompter, { name, version, runtime: preset, genera
  */
 async function askWorkers(prompter, { embeddingDim }) {
   const w = {
-    d1: null, pluginDb: null, vectorize: null, ai: false, tasks: true,
+    d1: null, pluginDb: null, vectorize: null, ai: false, tasks: true, workerLoader: false,
     // nodejs_compat v2 needs 2024-09-23 or later; that exact floor was also the hardcoded
     // value, which made it two years stale on the day it shipped.
     compatibilityDate: '2026-07-01',
@@ -369,6 +369,19 @@ async function askWorkers(prompter, { embeddingDim }) {
     }
   }
 
+  // Default TRUE. Dynamic Workers reached open beta in March 2026 and is available to
+  // everyone on the Workers Paid plan — which a drive already needs for D1 and Durable
+  // Objects — so the binding is the ordinary case rather than the exotic one. Still a
+  // question, because it is the difference between "plugin indexers run" and "plugin
+  // indexers are skipped and the drive raises an issue saying so".
+  w.workerLoader = await prompter.confirm(
+    '  Bind a Worker Loader so plugin indexers can run?',
+    { key: 'workers.loader.enabled', default: true,
+      hint: 'without it, plugin indexers are skipped — a plugin still installs and its '
+        + 'viewers work, but nothing it would have contributed to search appears. '
+        + 'Needs the Workers Paid plan; works in `wrangler dev` regardless' },
+  );
+
   if (await prompter.section('Vectorize (semantic search)', { key: 'workers.vectorize.enabled',
     blurb: 'sqlite-vec is a native artifact and cannot load here, so semantic search needs Vectorize.',
   })) {

package/src/render.js

@@ -434,6 +434,33 @@ function wranglerToml(plan) {
     L.push('');
   }
 
+  // Where PLUGIN INDEXERS run. A plugin's indexer is somebody else's code executing on
+  // the server, and a Worker cannot simply import it: the in-process runner loads code
+  // through a `data:` URL, which workerd refuses outright — so without this binding every
+  // plugin indexer fails on every file. (It used to fail silently; a deployment that
+  // cannot run them now skips them and raises an issue saying so.)
+  //
+  // A Worker Loader gives that code a real isolate with no bindings and no network beyond
+  // the one presigned URL the host hands it. Open beta since March 2026 on the Workers
+  // Paid plan — which a drive already needs for D1 and Durable Objects — and it works in
+  // `wrangler dev` on any plan.
+  //
+  // Billing is per unique Worker LOADED per day, not per file indexed: the loader is keyed
+  // by package digest, so a plugin costs one load a day however many files it walks.
+  if (w?.workerLoader) {
+    L.push('# Isolates for plugin indexers. See "Server indexers" in the README.');
+    L.push('[[worker_loaders]]');
+    L.push('binding = "LOADER"');
+    L.push('');
+  } else {
+    L.push('# [[worker_loaders]]        # plugin indexers run in isolates loaded through this.');
+    L.push('# binding = "LOADER"        # Needs the Workers Paid plan; works in `wrangler dev`');
+    L.push('#                           # on any plan. Without it a plugin that ships a server');
+    L.push('#                           # indexer still installs and its viewers work, but its');
+    L.push('#                           # indexers are skipped and the drive raises an issue.');
+    L.push('');
+  }
+
   if (w?.vectorize) {
     L.push('[[vectorize]]');
     L.push('binding = "VECTORIZE"');