Patch Changes
- f61586b: Fix: the vite plugins can be imported from a real npm install (#1895, BookShepherd report).
exports["./vite"],"./vite-plugin-debug"and"./gen/vite-plugin"pointed at raw.ts, and Node refuses to strip types undernode_modules— so anyvite.config.jsimportingqdadmVitePlugindied withERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING, takingnpm run devandnpm run buildwith it, on an error that never named qdadm. It never showed here because our examples consume through a workspace symlink, whose realpath escapesnode_modules. Those three entry points are now compiled todist/node/and built byprepack; everything the consumer's bundler compiles still ships as source, so raw-source consumption is unchanged. The consumer-smoke gate now imports every Node entry point for real and asks vite to resolve a config using the plugins — the previous gate typechecked the packed tarball without ever loading it, which is exactly how this shipped.@quazardous/qdadm/genremains source-only and still cannot be imported from Node: it mixes build-time codegen with a runtime factory that instantiates anEntityManager, and splitting it changes a published entry point.