create-vidra-app 0.4.0 → 0.5.1

package/templates/react-vite/src/{{projectName}}.Host/{{projectName}}.Host.csproj

@@ -1,6 +1,13 @@
 <Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
+    <!-- Pinned, not inferred: a Release Catalyst publish is universal
+         (maccatalyst-x64 + maccatalyst-arm64) while a Debug build takes
+         the host RID alone, and both share one obj/. Whichever restored
+         last owns project.assets.json, so a publish that no-ops its
+         restore can read an assets file with no x64 target and fail with
+         NETSDK1047. Naming the set here makes every restore write both. -->
+    <RuntimeIdentifiers Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'maccatalyst'">maccatalyst-x64;maccatalyst-arm64</RuntimeIdentifiers>
     <TargetFrameworks Condition="$([MSBuild]::IsOSPlatform('osx'))">net10.0-maccatalyst</TargetFrameworks>
     <TargetFrameworks Condition="$([MSBuild]::IsOSPlatform('windows'))">net10.0-windows10.0.19041.0</TargetFrameworks>
     <ValidateXcodeVersion>false</ValidateXcodeVersion>
@@ -62,9 +69,9 @@
       argument and expects it to do that work and exit without ever showing a
       window, and `vpk pack` inspects the assembly and warns when it finds the
       call outside the entry point. Entry-point shape is the one thing a package
-      reference cannot retrofit, so every Vidra app ships with it and the
-      Velopack line stays commented out until the app opts in. Mac Catalyst
-      already has a real `Main`, so it needs no equivalent switch.
+      reference cannot retrofit, so every Vidra app ships with it, live, from the
+      first scaffold. Mac Catalyst already has a real `Main`, so it needs no
+      equivalent switch.
     -->
     <DefineConstants Condition="$([MSBuild]::GetTargetPlatformIdentifier('$(TargetFramework)')) == 'windows'">$(DefineConstants);DISABLE_XAML_GENERATED_MAIN</DefineConstants>
 
@@ -88,8 +95,16 @@
 
   <ItemGroup>
     <PackageReference Include="Microsoft.Maui.Controls" Version="$(MauiVersion)" />
-    <PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="9.0.0" />
+    <PackageReference Include="Microsoft.Extensions.Logging.Debug" Version="10.0.10" />
     <PackageReference Include="Vidra.Hosting.Maui" Version="{{vidraVersion}}" />
+    <!--
+      Whole-app updates, via Velopack. Referenced from the first scaffold and
+      inert until vidra.config.ts names a native feed: ~280 KB of managed code
+      against a self-contained .NET + MAUI app, which is the price of never
+      having to retrofit an entry point, a package reference and a builder call
+      into an app that has already shipped.
+    -->
+    <PackageReference Include="Vidra.Updates.Native" Version="{{vidraVersion}}" />
   </ItemGroup>
 
 </Project>

package/templates/react-vite/ui/package.json

@@ -16,8 +16,8 @@
   "devDependencies": {
     "@types/react": "^19.0.0",
     "@types/react-dom": "^19.0.0",
-    "@vitejs/plugin-react": "^4.4.0",
-    "typescript": "^5.7.0",
-    "vite": "^6.0.0"
+    "@vitejs/plugin-react": "^6.0.5",
+    "typescript": "^7.0.2",
+    "vite": "^8.2.1"
   }
 }

package/templates/react-vite/ui/src/generated/vidra-access-policy.ts

@@ -0,0 +1,6 @@
+// Generated by the Vidra CLI. Do not edit.
+import { vidra } from "@vidra-dev/sdk";
+
+vidra.registerExpectedAccessFingerprint(
+  "f8e12289e430f3ecfce80c132a8b23e9539c041a0912b7c116feae722f510f68",
+);

package/templates/react-vite/ui/src/main.tsx

@@ -2,6 +2,7 @@ import { StrictMode } from "react";
 import { createRoot } from "react-dom/client";
 import App from "./App";
 import "./index.css";
+import "./generated/vidra-access-policy.js";
 
 createRoot(document.getElementById("root")!).render(
   <StrictMode>

package/templates/react-vite/ui/vite.config.ts

@@ -25,8 +25,11 @@ export default defineConfig({
     emptyOutDir: true,
     rollupOptions: {
       output: {
+        // `format: "iife"` already implies no code splitting, and since Vite 8
+        // saying so twice is a warning on every app build: "inlineDynamicImports
+        // option is ignored because codeSplitting: false is set". Output is
+        // byte-identical without it — still one file, still no import map.
         format: "iife",
-        inlineDynamicImports: true,
       },
     },
   },

package/templates/react-vite/vidra.config.ts

@@ -0,0 +1,33 @@
+import {
+  defineConfig,
+  events as builtInEvents,
+  native as builtInNative,
+} from "@vidra-dev/sdk/config";
+
+export default defineConfig({
+  bridge: {
+    allow: [
+      builtInNative.app.getInfo,
+      builtInNative.appWindow.center,
+      builtInNative.appWindow.configure,
+      builtInNative.appWindow.getCurrent,
+      builtInNative.appWindow.getSupport,
+      builtInNative.appWindow.maximize,
+      builtInNative.appWindow.minimize,
+      builtInNative.appWindow.restore,
+      builtInNative.appWindow.setTitle,
+      builtInNative.browser.open,
+      builtInNative.clipboard.getText,
+      builtInNative.notifications.requestPermission,
+      builtInNative.notifications.show,
+    ],
+    events: [
+      builtInEvents.appWindow.resized,
+      builtInEvents.appWindow.stateChanged,
+      builtInEvents.runtime.hotReloaded,
+    ],
+  },
+  updates: {
+    feed: "",
+  },
+});

package/bin/vidra.mjs

@@ -1,2 +0,0 @@
-#!/usr/bin/env node
-import("../dist/cli.js");