@lunora/vite 1.0.0-alpha.3 → 1.0.0-alpha.300

package/LICENSE.md

@@ -103,3 +103,9 @@ Unless required by applicable law or agreed to in writing, software distributed
 under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
 CONDITIONS OF ANY KIND, either express or implied. See the License for the
 specific language governing permissions and limitations under the License.
+
+<!-- DEPENDENCIES -->
+<!-- /DEPENDENCIES -->
+
+<!-- TYPE_DEPENDENCIES -->
+<!-- /TYPE_DEPENDENCIES -->

package/README.md

@@ -68,9 +68,11 @@ With no options, `lunora()` runs codegen on save, validates `wrangler.jsonc`, in
 
 ```ts
 lunora({
-    schemaDir: "lunora", // dir with schema.ts + function files
-    generatedDir: "lunora/_generated", // where api.ts/server.ts/dataModel.ts land
+    schemaDir: "lunora", // dir with schema.ts + function files (generated output lands in <schemaDir>/_generated)
     apiSpec: "openapi", // "openapi" | "openrpc" | "both" | "none"
+    target: "cloudflare", // deploy target the emitted ctx.* surface is tailored to
+    allowUnauthenticatedShardAccess: false, // composed class-A worker: allow a client-named shard / fan-out with no authorizeShard
+    shard: { cdc: true, reactiveCache: true }, // class-A only: shard DO config for the composed entry (class B/C set this in their own worker entry)
     studio: false, // disable the /__lunora studio
     overlay: false, // disable the runtime error overlay
     validateWrangler: false, // skip the wrangler.jsonc binding check
@@ -80,6 +82,21 @@ lunora({
 
 `lunora()` returns a flat `Plugin[]`; Vite flattens nested plugin arrays, so `plugins: [lunora()]` works without spreading.
 
+### Error overlay
+
+The overlay surfaces dev-time failures in the browser. Lunora ships **solution finders** that turn the common ones — missing/invalid `defineSchema`, reserved or duplicate table names, a bad `.jurisdiction(...)`, a non-literal `unique`, a binding that isn't re-exported by your worker entry, and runtime unique-constraint / optimistic-concurrency conflicts — into an actionable fix hint right in the overlay.
+
+`overlay` also accepts an options object forwarded to [`@visulima/vite-overlay`](https://www.npmjs.com/package/@visulima/vite-overlay), so you can add your own finders alongside Lunora's:
+
+```ts
+lunora({
+    overlay: {
+        // your finders run alongside Lunora's; either side can win per error via `priority`
+        solutionFinders: [myCustomFinder],
+    },
+});
+```
+
 > This README covers the basics. For the full API, options, and guides, see the **[documentation](https://lunora.sh/docs/packages/vite)**.
 
 ## Related