[Bug]: Vite custom font scanning all available font files including node_modules

[chunlampang]

Describe the feature

Since there are some font files (e.g. icon font) already handled by other plugin, unplugin-fonts is no need to inject those files. It just need to inject the configurated fonts instead of inject every available font files inside the build.
It is suggested that adding an option to disable control custom font.

Update - it is a bug

Vite custom font scanning all available font files including node_modules file on build

[chunlampang]

Are the following code repeated?

unplugin-fonts/src/index.ts

Lines 92 to 102 in a7e66d5

	tags.push({
	tag: 'link',
	injectTo: options?.custom?.injectTo ?? 'head-prepend',
	attrs: {
	rel: options?.custom?.prefetch ? 'prefetch' : 'preload',
	as: 'font',
	type: `font/${ext.replace('.', '')}`,
	href: join(base, file),
	crossorigin: 'anonymous',
	},
	})

unplugin-fonts/src/index.ts

Lines 126 to 136 in a7e66d5

	tags.push({
	tag: 'link',
	injectTo: options.custom?.injectTo ?? 'head-prepend',
	attrs: {
	rel: options.custom?.prefetch ? 'prefetch' : 'preload',
	as: 'font',
	type: `font/${ext.replace('.', '')}`,
	href: join(base, file),
	crossorigin: 'anonymous',
	},
	})

[segevfiner]

I'm hitting this as well, and this results in console warnings in my app, due to adding preload directives for fonts that are only used in async chunks that are not loaded with the app. This happens because the current code generates preload directives for all fonts in the bundle rather than only fonts included via custom which is undesirable IMHO.

[its2easy]

if you don't use custom fonts a quick fix is

UnpluginFonts({
  ...
  custom: {
    families: [],
    preload: false,
  },
}),

The proper way is probably to use linkFilter, but it's not in the docs