Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug Report][1.3.0] utilities/instance: `import * as Vue` keeps the whole Vapor runtime in VDOM-only bundles

Open Beginner friendly
  • Is something wrong?
#1,089 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
performance

Research direction

Start with packages/0/src/utilities/instance.ts, where the namespace import pulls all Vue exports into the bundle. Use the provided src/main.ts Vite reproduction to compare the generated bundle, and check that the fix preserves the current-instance behavior without including @vue/runtime-vapor. Done means a VDOM-only build no longer contains the Vapor runtime and the existing utility behavior remains intact.

Written by the indexing model from the issue text.

Description

Environment

Vuetify0 Version: 1.3.0
Vue Version: 3.6.0-rc.12
OS: Linux undefined (current)

Steps to reproduce
  1. npm i [email protected] @vuetify/[email protected] [email protected]
  2. index.html: <script type="module" src="/src/main.ts"></script>
  3. src/main.ts: import { useStack } from "@vuetify/v0"; import { createApp, h } from "vue"; createApp({ setup: () => { useStack(); return () => h("div", "hello"); } }).mount("#app");
  4. npx vite build: the JS bundle contains @vue/runtime-vapor (100.8 KB gzip; 24.9 KB with the @vuetify/v0 import removed)
Expected Behavior

A VDOM-only app that uses @vuetify/v0 does not bundle @vue/runtime-vapor.

Actual Behavior

utilities/instance.ts imports * as Vue and reads 'current' + 'Instance' in vueExports, so the bundler keeps every export of vue, including the Vapor runtime that Vue 3.6 re-exports. Vite 8.3.5 build, gzip JS: Vue alone 24.9 KB; with useStack from @vuetify/v0 1.3.0 100.8 KB (@vue/runtime-vapor bundled); the same with instance.mjs changed to import { getCurrentInstance } from 'vue' 30.3 KB (no @vue/runtime-vapor).

Reproduction Link

https://github.com/vuetifyjs/0/blob/376f9e77dd80776bd15f18a0071e355fa0ef1473/packages/0/src/utilities/instance.ts#L3-L24

Other comments

Named imports keep the rest of vue tree-shakable. We patched instance.mjs locally to import { getCurrentInstance } from 'vue' because our app has no Vapor components; keeping Vapor support would need a named currentInstance import where Vue >= 3.6 is guaranteed.

Dominant language
TypeScript
Stars
740
Forks
10
Avg merge
1d 12h
Merged PRs (30d)
77

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from vuetifyjs/0

All issues in vuetifyjs/0

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.