The Vue components, composables, tokens, and CSS all collapse into a single @vanduo-oss/vd3 package; the four canvas add-ons move into the @vanduo-oss/vd3-cbun bundle, each on its own subpath.

The old /vue subpath drops away — where you wrote @vanduo-oss/charts/vue you now import from @vanduo-oss/vd3-cbun/charts. Secondary subpaths follow the same rule (.../hex-grid/hex-math, .../charts/css).

The VanduoVue plugin identifier and its themeDefaults option are unchanged — only the import source moves. In your entry file, retarget the plugin import and the stylesheet to @vanduo-oss/vd3:

// main.ts — vanduo v2 (the @vanduo-oss/vue line)
import { createApp } from 'vue';
import { VanduoVue } from '@vanduo-oss/vue';
import '@vanduo-oss/vue/css';
import App from './App.vue';

createApp(App).use(VanduoVue, { themeDefaults }).mount('#app');

// main.ts — vd3 (only the two import sources change)
import { createApp } from 'vue';
import { VanduoVue } from '@vanduo-oss/vd3';
import '@vanduo-oss/vd3/css';
import App from './App.vue';

createApp(App).use(VanduoVue, { themeDefaults }).mount('#app');

vd3 restores the twelve delegating / DOM-scan composables as first-class Vue composables. Their useX(rootRef) call signature is unchanged, so existing call sites port over untouched — swap the import from the old package to @vanduo-oss/vd3 and you are done:

useDropdownuseDraggableuseImageBoxuseRippleuseSpotlightuseTimelineuseExpandingCardsuseFlowuseTabsuseValidateuseSearchusePopover

// vanduo v2 — these composables were thin shims that delegated to the
// zero-build global runtime, which the app had to bootstrap once at startup.
import { useDropdown, useTabs } from '@vanduo-oss/vue';

const root = ref<HTMLElement | null>(null);
useDropdown(root);
useTabs(root);

// vd3 — same call signature; only the import source changes. The composables
// are now self-contained Vue, so there is nothing to load or init after mount.
import { useDropdown, useTabs } from '@vanduo-oss/vd3';

const root = ref<HTMLElement | null>(null);
useDropdown(root); // still useX(rootRef) — existing call sites port unchanged
useTabs(root);     // several now also return an optional controller (a superset)

The big change is under the hood: in v2 these composables delegated to the framework's zero-build global runtime, which an app bootstrapped once at startup. vd3 rewrites them as self-contained Vue — that runtime, and the startup call it needed, are gone, so there is nothing to load or initialise after mount. Several composables now also return an optional controller, which is a backward-compatible superset: call sites that ignored the old void result are unaffected.

vd3 also drops Pinia — its sole peer dependency is vue >=3.3. The v2 theme store is now the reactive useThemePreference() singleton, and useToast() / useToastStore() stay available as plain reactive singletons rather than a defineStore.