Stop bundling duplicate DuckDB wasm chunks in notebook Vite build #342

New issue

Closed

opened 2026-06-06 11:35:17 +00:00 by steve · 0 comments

steve commented

2026-06-06 11:35:17 +00:00

Owner

Describe the issue.

Problem

Goal

Scope

Non-goals

Acceptance Criteria

Implementation Notes

Suggested Files or Specs To Inspect

Validation Commands

Follow-up to #300 — Reduce notebook plugin release size by externalizing heavy runtime assets

Follow-up Tasks

Implementation Summary

Set notebook main Vite build emptyOutDir: true so stale hashed duckdb JS chunks and main.umd.js are not copied into release inputs; removed @lapis-notes/api/storage/path bare require from notebook-plugin-runtime-assets via local joinPluginPath(). Dry-run publish zip dropped from ~778 MiB to ~150 MiB (optional ~106 MiB external duckdb/ assets only).

Describe the issue. ## Problem ## Goal ## Scope ## Non-goals ## Acceptance Criteria ## Implementation Notes ## Suggested Files or Specs To Inspect ## Validation Commands ## Related Issues - Follow-up to #300 — [Reduce notebook plugin release size by externalizing heavy runtime assets](../closed/300-reduce-notebook-plugin-release-size-by-externalizing-heavy-runtime-assets.md) ## Follow-up Tasks ## Implementation Summary Set notebook main Vite build emptyOutDir: true so stale hashed duckdb JS chunks and main.umd.js are not copied into release inputs; removed @lapis-notes/api/storage/path bare require from notebook-plugin-runtime-assets via local joinPluginPath(). Dry-run publish zip dropped from ~778 MiB to ~150 MiB (optional ~106 MiB external duckdb/ assets only).

steve

2026-06-06 11:35:17 +00:00