vite-plugin-taro 0.6.17 → 0.6.18

package/dist/node/plugins/wx/styles/plugins.d.ts

@@ -8,7 +8,7 @@ type JavaScriptArtifact = Readonly<{
 }>;
 /** Vite plugin with the development-host operation that finalizes one coherent WX style/JavaScript transaction. */
 export type WxStylePlugin = Plugin & Readonly<{
-    /** Converts patch factories and publishes their matching global WXSS through the host's atomic writer. */
+    /** Neutralizes browser CSS payloads and publishes their matching global WXSS through the host's atomic writer. */
     finalizeUpdate: <Artifact extends JavaScriptArtifact>(artifacts: readonly Artifact[], writeWxss: (wxss: string) => Promise<void>) => Promise<readonly Artifact[]>;
 }>;
 /**
@@ -93,7 +93,8 @@ export type WxStylePlugin = Plugin & Readonly<{
  * The development host calls `finalizeUpdate()` after Rolldown produces patch factories or a complete-output notification.
  * Finalization uses the `PluginContext` captured by `buildStart`, so it observes the same current graph as the compiler. After
  * all conversion succeeds, the host's atomic writer publishes changed WXSS before `finalizeUpdate()` returns converted patch
- * factories. The patch publisher therefore cannot expose newer JavaScript class identities before matching selectors exist.
+ * factories. Their captured Vite CSS literals are emptied first; factories, exports, changed IDs, and sequences remain intact.
+ * The patch publisher therefore cannot expose newer JavaScript class identities before matching selectors exist.
  * `publishedWxss` advances only after a successful write and suppresses byte-identical writes that would otherwise trigger
  * unnecessary WeChat DevTools reload events.
  *

package/dist/node/plugins/wx/styles/plugins.js

@@ -98,7 +98,8 @@ const wxStyleOptions = {
  * The development host calls `finalizeUpdate()` after Rolldown produces patch factories or a complete-output notification.
  * Finalization uses the `PluginContext` captured by `buildStart`, so it observes the same current graph as the compiler. After
  * all conversion succeeds, the host's atomic writer publishes changed WXSS before `finalizeUpdate()` returns converted patch
- * factories. The patch publisher therefore cannot expose newer JavaScript class identities before matching selectors exist.
+ * factories. Their captured Vite CSS literals are emptied first; factories, exports, changed IDs, and sequences remain intact.
+ * The patch publisher therefore cannot expose newer JavaScript class identities before matching selectors exist.
  * `publishedWxss` advances only after a successful write and suppresses byte-identical writes that would otherwise trigger
  * unnecessary WeChat DevTools reload events.
  *
@@ -278,8 +279,13 @@ export function createWxStylePlugin(applicationEntryIds) {
         },
         /** Finalizes one development result and publishes matching WXSS before exposing converted patch factories. */
         finalizeUpdate: async (artifacts, writeWxss) => {
+            // CSS is already captured for physical publication, so its browser payload need not enter JavaScript conversion.
+            const javaScript = artifacts.map((artifact) => ({
+                code: neutralizeViteCssPayload(artifact.code),
+                filename: artifact.filename
+            }));
             // Step 1: complete every fallible conversion against one snapshot of the current module graph.
-            const output = await finalizeCurrentOutput(graphContext, artifacts);
+            const output = await finalizeCurrentOutput(graphContext, javaScript);
             // Step 2: publish changed WXSS first so DevTools cannot observe JavaScript containing newer class identities.
             if (output.wxss !== publishedWxss) {
                 await writeWxss(output.wxss);
@@ -421,6 +427,26 @@ function isApplicationStyle(id) {
     const parameters = new URLSearchParams(query);
     return ignoredStyleQueries.every((parameter) => !parameters.has(parameter));
 }
+/**
+ * Empties only the CSS bytes in Vite's generated browser transport:
+ *
+ * ```js
+ * const __vite__css = ".app { color: red }";
+ * __vite__updateStyle(__vite__id, __vite__css);
+ * ```
+ *
+ * becomes:
+ *
+ * ```js
+ * const __vite__css = "";
+ * __vite__updateStyle(__vite__id, __vite__css);
+ * ```
+ *
+ * The surrounding factory, CSS Module exports, changed IDs, and patch sequence remain unchanged.
+ */
+function neutralizeViteCssPayload(code) {
+    return code.replace(/(\b(?:const|let|var)\s+__vite__css[\w$]*\s*=\s*)"(?:\\[\s\S]|[^"\\])*"(?=;\s*\b__vite__updateStyle[\w$]*\s*\()/g, '$1""');
+}
 /** Detects source forms that require Tailwind compilation before Vite processes the resulting CSS. */
 function isTailwindRoot(code) {
     // Tailwind v4 uses package imports; legacy directives remain accepted because the generator supports both forms.

package/dist/node/utils/modules.js

@@ -2,11 +2,11 @@ import path from 'node:path';
 import { normalizePath } from 'vite';
 /** Resolves the source file for the configured App component. */
 export function resolveAppComponentPath({ appPath, projectRoot }) {
-    return path.resolve(projectRoot, appPath);
+    return normalizePath(path.resolve(projectRoot, appPath));
 }
 /** Resolves the source file for one configured Page component. */
 export function resolvePageComponentPath({ pagePath, projectRoot }) {
-    return path.resolve(projectRoot, 'src', `${pagePath}.tsx`);
+    return normalizePath(path.resolve(projectRoot, 'src', `${pagePath}.tsx`));
 }
 /** Creates a portable import for one configured Page component. */
 export function createPageComponentImportPath(options) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "vite-plugin-taro",
-  "version": "0.6.17",
+  "version": "0.6.18",
   "author": "sep2",
   "description": "Vite 8 plugin for building one React/Taro codebase for WeChat Mini Program and H5 targets.",
   "type": "module",
@@ -60,12 +60,12 @@
     "@tailwindcss/oxide": "4.3.3",
     "@tarojs/components": "4.2.1",
     "@tarojs/helper": "4.2.1",
-    "@tarojs/plugin-framework-react": "npm:vite-plugin-taro-plugin-framework-react@0.6.17",
+    "@tarojs/plugin-framework-react": "npm:vite-plugin-taro-plugin-framework-react@0.6.18",
     "@tarojs/plugin-platform-h5": "4.2.1",
     "@tarojs/plugin-platform-weapp": "4.2.1",
-    "@tarojs/react": "npm:vite-plugin-taro-react@0.6.17",
+    "@tarojs/react": "npm:vite-plugin-taro-react@0.6.18",
     "@tarojs/router": "4.2.1",
-    "@tarojs/runtime": "npm:vite-plugin-taro-runtime@0.6.17",
+    "@tarojs/runtime": "npm:vite-plugin-taro-runtime@0.6.18",
     "@tarojs/taro": "4.2.1",
     "@vitejs/plugin-react": "^6.1.0",
     "@weapp-tailwindcss/postcss": "3.2.11",

package/src/node/plugins/wx/styles/plugins.ts

@@ -46,7 +46,7 @@ type JavaScriptArtifact = Readonly<{
 /** Vite plugin with the development-host operation that finalizes one coherent WX style/JavaScript transaction. */
 export type WxStylePlugin = Plugin &
     Readonly<{
-        /** Converts patch factories and publishes their matching global WXSS through the host's atomic writer. */
+        /** Neutralizes browser CSS payloads and publishes their matching global WXSS through the host's atomic writer. */
         finalizeUpdate: <Artifact extends JavaScriptArtifact>(
             artifacts: readonly Artifact[],
             writeWxss: (wxss: string) => Promise<void>
@@ -146,7 +146,8 @@ const wxStyleOptions = {
  * The development host calls `finalizeUpdate()` after Rolldown produces patch factories or a complete-output notification.
  * Finalization uses the `PluginContext` captured by `buildStart`, so it observes the same current graph as the compiler. After
  * all conversion succeeds, the host's atomic writer publishes changed WXSS before `finalizeUpdate()` returns converted patch
- * factories. The patch publisher therefore cannot expose newer JavaScript class identities before matching selectors exist.
+ * factories. Their captured Vite CSS literals are emptied first; factories, exports, changed IDs, and sequences remain intact.
+ * The patch publisher therefore cannot expose newer JavaScript class identities before matching selectors exist.
  * `publishedWxss` advances only after a successful write and suppresses byte-identical writes that would otherwise trigger
  * unnecessary WeChat DevTools reload events.
  *
@@ -353,8 +354,14 @@ export function createWxStylePlugin(applicationEntryIds: readonly string[]): WxS
             artifacts: readonly Artifact[],
             writeWxss: (wxss: string) => Promise<void>
         ): Promise<readonly Artifact[]> => {
+            // CSS is already captured for physical publication, so its browser payload need not enter JavaScript conversion.
+            const javaScript = artifacts.map((artifact) => ({
+                code: neutralizeViteCssPayload(artifact.code),
+                filename: artifact.filename
+            }))
+
             // Step 1: complete every fallible conversion against one snapshot of the current module graph.
-            const output = await finalizeCurrentOutput(graphContext, artifacts)
+            const output = await finalizeCurrentOutput(graphContext, javaScript)
 
             // Step 2: publish changed WXSS first so DevTools cannot observe JavaScript containing newer class identities.
             if (output.wxss !== publishedWxss) {
@@ -549,6 +556,30 @@ function isApplicationStyle(id: string): boolean {
     return ignoredStyleQueries.every((parameter) => !parameters.has(parameter))
 }
 
+/**
+ * Empties only the CSS bytes in Vite's generated browser transport:
+ *
+ * ```js
+ * const __vite__css = ".app { color: red }";
+ * __vite__updateStyle(__vite__id, __vite__css);
+ * ```
+ *
+ * becomes:
+ *
+ * ```js
+ * const __vite__css = "";
+ * __vite__updateStyle(__vite__id, __vite__css);
+ * ```
+ *
+ * The surrounding factory, CSS Module exports, changed IDs, and patch sequence remain unchanged.
+ */
+function neutralizeViteCssPayload(code: string): string {
+    return code.replace(
+        /(\b(?:const|let|var)\s+__vite__css[\w$]*\s*=\s*)"(?:\\[\s\S]|[^"\\])*"(?=;\s*\b__vite__updateStyle[\w$]*\s*\()/g,
+        '$1""'
+    )
+}
+
 /** Detects source forms that require Tailwind compilation before Vite processes the resulting CSS. */
 function isTailwindRoot(code: string): boolean {
     // Tailwind v4 uses package imports; legacy directives remain accepted because the generator supports both forms.

package/src/node/utils/modules.ts

@@ -13,12 +13,12 @@ type PageComponentPathOptions = {
 
 /** Resolves the source file for the configured App component. */
 export function resolveAppComponentPath({ appPath, projectRoot }: AppComponentPathOptions): string {
-    return path.resolve(projectRoot, appPath)
+    return normalizePath(path.resolve(projectRoot, appPath))
 }
 
 /** Resolves the source file for one configured Page component. */
 export function resolvePageComponentPath({ pagePath, projectRoot }: PageComponentPathOptions): string {
-    return path.resolve(projectRoot, 'src', `${pagePath}.tsx`)
+    return normalizePath(path.resolve(projectRoot, 'src', `${pagePath}.tsx`))
 }
 
 /** Creates a portable import for one configured Page component. */