@vizejs/vite-plugin 0.332.0 → 0.334.0

package/dist/index.d.mts

@@ -1,4 +1,4 @@
-import { a as VizeVueVersion, c as VizeInspectorLintPlanRequest, d as LoadConfigOptions, f as ResolvedVizeConfig, i as VizeOptions, l as VizeInspectorOptions, m as VizeConfig, n as MacroArtifact, o as VizeVueFeatures, p as UserConfigExport, r as VizeCompatibilityOptions, s as VizeInspectorLintPlanProvider, t as CompiledModule, u as ConfigEnv } from "./types-DR5IFFd7.mjs";
+import { a as VizeVueVersion, c as VizeInspectorLintPlanRequest, d as LoadConfigOptions, f as ResolvedVizeConfig, i as VizeOptions, l as VizeInspectorOptions, m as VizeConfig, n as MacroArtifact, o as VizeVueFeatures, p as UserConfigExport, r as VizeCompatibilityOptions, s as VizeInspectorLintPlanProvider, t as CompiledModule, u as ConfigEnv } from "./types-T_Fu8G5I.mjs";
 import { Plugin } from "vite";
 
 //#region src/virtual.d.ts

package/dist/index.mjs

@@ -341,9 +341,20 @@ function toNativeCssAliasRule(rule) {
 }
 //#endregion
 //#region src/utils/filter.ts
+/**
+* Defaults the filter falls back to, and what the `vite:vue` shim reports
+* through `api.include` / `api.exclude` when neither is configured (#3227).
+*
+* `DEFAULT_INCLUDE_PATTERN` is `@vitejs/plugin-vue`'s own default.
+* `DEFAULT_EXCLUDE_PATTERN` has no upstream counterpart — plugin-vue leaves
+* `exclude` undefined — so the shim reports the pattern Vize actually filters
+* on rather than an upstream-shaped `undefined` it does not honor.
+*/
+const DEFAULT_INCLUDE_PATTERN = /\.vue$/;
+const DEFAULT_EXCLUDE_PATTERN = /node_modules/;
 function createFilter(include, exclude) {
-	const includePatterns = include ? Array.isArray(include) ? include : [include] : [/\.vue$/];
-	const excludePatterns = exclude ? Array.isArray(exclude) ? exclude : [exclude] : [/node_modules/];
+	const includePatterns = include ? Array.isArray(include) ? include : [include] : [DEFAULT_INCLUDE_PATTERN];
+	const excludePatterns = exclude ? Array.isArray(exclude) ? exclude : [exclude] : [DEFAULT_EXCLUDE_PATTERN];
 	return (id) => {
 		const matchInclude = includePatterns.some((pattern) => matchesFilterPattern(pattern, id));
 		const matchExclude = excludePatterns.some((pattern) => matchesFilterPattern(pattern, id));
@@ -3044,7 +3055,16 @@ async function handleHotUpdateEnvironmentHook(state, environment, options) {
 }
 //#endregion
 //#region src/plugin/compat.ts
-function createVueCompatPlugin(state) {
+/**
+* The `vite:vue` shim a host framework probes for a Vue plugin.
+*
+* `api.include` / `api.exclude` report the patterns behind `state.filter`, and
+* assigning them rewrites the plugin's own options — the only window where that
+* is meaningful is before `configResolved` builds the filter, so a later write
+* throws rather than silently doing nothing (#3227). Upstream guards the same
+* way, keyed on its `options` hook instead.
+*/
+function createVueCompatPlugin(state, options) {
 	let compilerSfc = null;
 	const loadCompilerSfc = () => {
 		if (!compilerSfc) try {
@@ -3057,16 +3077,36 @@ function createVueCompatPlugin(state) {
 		}
 		return compilerSfc;
 	};
+	const configured = () => state.initialized ? state.mergedOptions : options;
+	const assertUnresolved = (name) => {
+		if (state.initialized) throw new Error(`${name} cannot be updated after the filter is resolved`);
+	};
 	return {
 		name: "vite:vue",
-		api: { get options() {
-			return {
-				compiler: loadCompilerSfc(),
-				isProduction: state.isProduction ?? false,
-				root: state.root ?? process.cwd(),
-				template: {}
-			};
-		} }
+		api: {
+			get options() {
+				return {
+					compiler: loadCompilerSfc(),
+					isProduction: state.isProduction ?? false,
+					root: state.root ?? process.cwd(),
+					template: {}
+				};
+			},
+			get include() {
+				return configured().include ?? DEFAULT_INCLUDE_PATTERN;
+			},
+			set include(value) {
+				assertUnresolved("include");
+				options.include = value;
+			},
+			get exclude() {
+				return configured().exclude ?? DEFAULT_EXCLUDE_PATTERN;
+			},
+			set exclude(value) {
+				assertUnresolved("exclude");
+				options.exclude = value;
+			}
+		}
 	};
 }
 function normalizeVirtualStyleId(id) {
@@ -3690,11 +3730,18 @@ function parseDefine(value) {
 		return value;
 	}
 }
-/** Resolve Vue runtime defines with plugin-vue's precedence and defaults. */
-function resolveVueFeatureDefines(features, define, command) {
+/**
+* Resolve Vue runtime defines with plugin-vue's precedence and defaults.
+*
+* `__VUE_PROD_DEVTOOLS__` used to be `command === "serve"`, which left no way to
+* enable devtools for a production build (#3227). It now follows plugin-vue's
+* OR semantics, and defaults to `false` in dev as upstream does: a development
+* build enables devtools through Vue's own `__DEV__`, not through this flag.
+*/
+function resolveVueFeatureDefines(features, define) {
 	return {
 		__VUE_OPTIONS_API__: features?.optionsAPI ?? parseDefine(define?.__VUE_OPTIONS_API__) ?? true,
-		__VUE_PROD_DEVTOOLS__: command === "serve",
+		__VUE_PROD_DEVTOOLS__: (features?.prodDevtools || parseDefine(define?.__VUE_PROD_DEVTOOLS__)) ?? false,
 		__VUE_PROD_HYDRATION_MISMATCH_DETAILS__: (features?.prodHydrationMismatchDetails || parseDefine(define?.__VUE_PROD_HYDRATION_MISMATCH_DETAILS__)) ?? false
 	};
 }
@@ -3749,14 +3796,14 @@ function vize(options = {}) {
 		logger: createLogger(options.debug ?? false)
 	};
 	return [
-		createVueCompatPlugin(state),
+		createVueCompatPlugin(state, options),
 		{
 			name: "vite-plugin-vize",
 			enforce: "pre",
-			config(userConfig, env) {
+			config(userConfig) {
 				patchCssModuleGenerateScopedName(userConfig);
 				return {
-					define: resolveVueFeatureDefines(options.features, userConfig.define, env.command),
+					define: resolveVueFeatureDefines(options.features, userConfig.define),
 					optimizeDeps: { exclude: ["virtual:vize-styles"] }
 				};
 			},

package/dist/internal/config-bridge.d.mts

@@ -1,4 +1,4 @@
-import { f as ResolvedVizeConfig } from "../types-DR5IFFd7.mjs";
+import { f as ResolvedVizeConfig } from "../types-T_Fu8G5I.mjs";
 import { ResolvedConfig } from "vite";
 
 //#region src/internal/config-bridge.d.ts

package/dist/{types-DR5IFFd7.d.mts → types-T_Fu8G5I.d.mts}

@@ -730,6 +730,11 @@ interface VizeVueFeatures {
    * @default true
    */
   optionsAPI?: boolean;
+  /**
+   * Enable Vue devtools support in production bundles.
+   * @default false
+   */
+  prodDevtools?: boolean;
   /**
    * Enable detailed hydration mismatch errors in production bundles.
    * @default false

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vizejs/vite-plugin",
-  "version": "0.332.0",
+  "version": "0.334.0",
   "description": "High-performance native Vite plugin for Vue SFC compilation powered by Vize",
   "keywords": [
     "compiler",
@@ -45,10 +45,10 @@
     "access": "public"
   },
   "dependencies": {
-    "@vizejs/native": "0.332.0",
+    "@vizejs/native": "0.334.0",
     "oxc-parser": "0.133.0",
     "tinyglobby": "0.2.16",
-    "vize": "0.332.0"
+    "vize": "0.334.0"
   },
   "devDependencies": {
     "@types/node": "25.9.2",