@ethercorps/sveltekit-og 4.4.0-next.0 → 4.4.0-next.1

package/dist/plugin.d.ts

@@ -2,5 +2,16 @@ import { unwasm, type UnwasmPluginOptions } from "unwasm/plugin";
 import type { Plugin as VitePlugin } from "vite";
 type Plugin = ReturnType<typeof unwasm>;
 export declare function rollupWasm(options?: UnwasmPluginOptions): Plugin;
+/**
+ * Vite plugin: wires the wasm loader into the SSR bundle only. The client build
+ * (e.g. the /client entry) loads its wasm through Vite's own asset handling, and
+ * unwasm would break that.
+ *
+ * Gated at runtime rather than by Vite version: `import { version } from "vite"`
+ * resolves to this package's own copy of vite, not the consumer's.
+ * - Vite 6+: `applyToEnvironment` keeps the plugin off the client environment.
+ * - Vite 5: each hook no-ops unless the call carries `{ ssr: true }`.
+ * `apply: "build"` keeps parity with the previous `build.rollupOptions.plugins` wiring.
+ */
 export declare function sveltekitOG(options?: UnwasmPluginOptions): VitePlugin;
 export {};

package/dist/plugin.js

@@ -6,24 +6,49 @@ export function rollupWasm(options) {
         ...options,
     });
 }
-export function sveltekitOG(options) {
+/**
+ * Is this hook call for the server bundle? Vite 6+ (SvelteKit 3 builds through the
+ * Environment API) exposes `this.environment`; Vite 5 (SvelteKit 2 runs separate
+ * client and SSR builds) passes `{ ssr }` as the hook's last argument instead.
+ */
+function isServer(ctx, args) {
+    if (ctx.environment)
+        return ctx.environment.config.consumer === "server";
+    const last = args[args.length - 1];
+    return typeof last === "object" && last !== null && last.ssr === true;
+}
+function serverOnly(hook) {
+    if (!hook)
+        return hook;
     return {
-        name: "vite-plugin-sveltekit-og",
-        // run after sveltekit(), whose config hook is what sets build.ssr
-        enforce: "post",
-        // SSR bundle only: the client build (e.g. the /client entry) loads its wasm
-        // through Vite's own asset handling, and unwasm would break that. Vite computes
-        // env.isSsrBuild before SvelteKit sets build.ssr, so check the merged config too.
-        config(config, { isSsrBuild }) {
-            if (!isSsrBuild && !config.build?.ssr)
-                return;
-            return {
-                build: {
-                    rollupOptions: {
-                        plugins: [rollupWasm(options)],
-                    },
-                },
-            };
+        ...hook,
+        handler(...args) {
+            return isServer(this, args) ? hook.handler.apply(this, args) : null;
         },
     };
 }
+/**
+ * Vite plugin: wires the wasm loader into the SSR bundle only. The client build
+ * (e.g. the /client entry) loads its wasm through Vite's own asset handling, and
+ * unwasm would break that.
+ *
+ * Gated at runtime rather than by Vite version: `import { version } from "vite"`
+ * resolves to this package's own copy of vite, not the consumer's.
+ * - Vite 6+: `applyToEnvironment` keeps the plugin off the client environment.
+ * - Vite 5: each hook no-ops unless the call carries `{ ssr: true }`.
+ * `apply: "build"` keeps parity with the previous `build.rollupOptions.plugins` wiring.
+ */
+export function sveltekitOG(options) {
+    const wasm = rollupWasm(options);
+    // `applyToEnvironment` only exists in Vite 6+ types; this package compiles against Vite 5.
+    const plugin = {
+        ...wasm,
+        name: "vite-plugin-sveltekit-og",
+        apply: "build",
+        applyToEnvironment: (env) => env.config.consumer === "server",
+        resolveId: serverOnly(wasm.resolveId),
+        load: serverOnly(wasm.load),
+        transform: serverOnly(wasm.transform),
+    };
+    return plugin;
+}

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@ethercorps/sveltekit-og",
-	"version": "4.4.0-next.0",
+	"version": "4.4.0-next.1",
 	"license": "MIT",
 	"homepage": "https://sveltekit-og.dev",
 	"repository": "github:etherCorps/sveltekit-og",