@base44-preview/vite-plugin 1.0.44-pr.131.133cb56 → 1.0.44-pr.131.f7a9bda

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/visual-edit-plugin.md +1 -1
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@base44-preview/vite-plugin",
3
- "version": "1.0.44-pr.131.133cb56",
3
+ "version": "1.0.44-pr.131.f7a9bda",
4
4
  "description": "The Vite plugin for base44 based applications",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/src/visual-edit-plugin.md CHANGED
@@ -59,7 +59,7 @@ It adds two HTML `data-*` attributes to every JSX element:
59
59
  ### Plugin Ordering
60
60
 
61
61
  - `enforce: "pre"` runs this before all `normal`/`post` transforms. Among other `enforce: "pre"` plugins, array position in `vite.config` decides, so `base44()` must be listed before `tanstackStart()`: TanStack's code splitter is also `pre`, and tagging its output would point `data-source-location` at the wrong lines
62
- - It also relies on Vite loading a queried id (`route.jsx?tsr-split=component`) from disk, so the split module's transform input is the original file, not the splitter's output. Both ids then tag identically, which keeps SSR and client hydration in agreement. Tags must come from raw JSX: tagging a rewritten file points `data-source-location` at generated lines
62
+ - This is critical because the plugin needs to process raw JSX before any other plugin modifies it
63
63
 
64
64
  ---
65
65