/**
 * Locate the `czap-compute.wasm` artifact shipped inside `@czap/core`.
 *
 * Resolved through THIS plugin's own dependency edge — `@czap/vite` depends on
 * `@czap/core` — via `import.meta.url`, NOT the consumer's project root. That is
 * the canonical pnpm-nesting-safe "a package finds its dependency's asset"
 * pattern: it works even when the app installs only `@czap/astro`/`liteship` and
 * pnpm's strict linker keeps `@czap/core` out of top-level `node_modules`, and it
 * resolves the EXACT `@czap/core` this `@czap/vite` was built against (so the
 * kernel matches the plugin, not whatever version the app may also pin).
 *
 * Split into its own module so tests can `vi.mock` it to simulate a consumer
 * with no resolvable binary (a same-module internal call would be unmockable).
 *
 * @module
 */
/**
 * Resolve `@czap/core`'s shipped `dist/czap-compute.wasm`, or `null` when
 * `@czap/core` (or its wasm) is absent — a 0.2.0 install, or none — so callers
 * fall through to the next WASM source.
 */
export declare function resolvePackagedWasm(): string | null;
//# sourceMappingURL=wasm-package-resolve.d.ts.map