fix: add wasm plugin to campaign-planner vite build entry
The folk-campaign-planner imports SocialsLocalFirstClient which pulls in Automerge WASM — needs vite-plugin-wasm and alias like other local-first module builds. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
parent
ec83f5c9c1
commit
ed837d8e4f
|
|
@ -635,11 +635,18 @@ export default defineConfig({
|
|||
resolve(__dirname, "dist/modules/rsocials/socials.css"),
|
||||
);
|
||||
|
||||
// Build campaign planner component
|
||||
// Build campaign planner component (with Automerge WASM support via local-first-client)
|
||||
await build({
|
||||
configFile: false,
|
||||
root: resolve(__dirname, "modules/rsocials/components"),
|
||||
plugins: [wasm()],
|
||||
resolve: {
|
||||
alias: {
|
||||
'@automerge/automerge': resolve(__dirname, 'node_modules/@automerge/automerge'),
|
||||
},
|
||||
},
|
||||
build: {
|
||||
target: "esnext",
|
||||
emptyOutDir: false,
|
||||
outDir: resolve(__dirname, "dist/modules/rsocials"),
|
||||
lib: {
|
||||
|
|
|
|||
Loading…
Reference in New Issue