Bundle size increases with the plugin when used in a quasar project

Hii @antfu, When a normal build is done on a quasar project, the build bundle size is 500kb smaller than a build with the plugin used.

Steps to reproduce

• create a new quasar cli project
• do a normal build
• check dist/spa folder size
• install unplugin-auto-import
• add it in quasar config with the following presets installed

 chainWebpack(chain) {
        chain.plugin('unplugin-auto-import').use(
          AutoImportPlugin({
            // targets to transform
            include: [
              /\.[tj]sx?$/, // .ts, .tsx, .js, .jsx
              /\.vue$/,
              /\.vue\?vue/, // .vue
              /\.md$/, // .md
            ],

            // global imports to register
            imports: [
              // presets
              'vue',
              'vue-router',
              'vuex',
              'quasar',
            ],
          })
        );
      },

• remove all vue API imports and run a build
• check dist/spa folder size
• it’s higher than that of the normal build

What’s expected

• The bundle size should remain the same because we have Tree shaking in place

What happenes

• The bundle size with the plugin is larger than without the plugin

Please let me know if you need a repo to reproduce. I did it with a project with around 20 .vue files and 10 plus .ts files

[userquin]

But it doesn’t add the the full esm prod bundle without the plugin. Do you think it’s kind of conflicting with the plugin? I mean the tree shaking of quasar conflicting with the plugin in any way?

Try file an issue on quasar repo, maybe there can address this, or wait to @antfu review.

[userquin]

without unplugin-auto-import: