@nuasite/cms 0.22.0 → 0.22.2

package/dist/editor.js

@@ -381,7 +381,7 @@ function CS(t, e) {
 function ES(t, e) {
   return typeof e == "function" ? e(t) : e;
 }
-const J_ = "0.22.0", j_ = J_, ct = {
+const J_ = "0.22.2", j_ = J_, ct = {
   /** Highlight overlay for hovered elements */
   HIGHLIGHT: 2147483644,
   /** Hover outline for elements/components */

package/package.json

@@ -14,7 +14,7 @@
     "directory": "packages/astro-cms"
   },
   "license": "Apache-2.0",
-  "version": "0.22.0",
+  "version": "0.22.2",
   "module": "src/index.ts",
   "types": "src/index.ts",
   "type": "module",

package/src/index.ts

@@ -58,9 +58,9 @@ export interface NuaCmsOptions extends CmsMarkerOptions {
 	}>
 	/**
 	 * Enable polling for file watching.
-	 * Ensures reliable change detection after CMS edits.
-	 * Set to `false` to use native fs events instead.
-	 * @default true
+	 * Set to `true` on filesystems that don't support native events (e.g. network mounts).
+	 * E2B sandboxes use ext4 with full inotify support, so polling is unnecessary.
+	 * @default false
 	 */
 	usePolling?: boolean
 }
@@ -85,7 +85,7 @@ export default function nuaCms(options: NuaCmsOptions = {}): AstroIntegration {
 		componentDirs = ['src/components'],
 		contentDir = 'src/content',
 		mdxComponentDirs,
-		usePolling = true,
+		usePolling = false,
 		seo = { trackSeo: true, markTitle: true, parseJsonLd: true },
 	} = options
 

package/src/vite-plugin.ts

@@ -1,3 +1,5 @@
+import { watch } from 'node:fs'
+import { join } from 'node:path'
 import type { Plugin } from 'vite'
 import { expectedDeletions } from './dev-middleware'
 import type { ManifestWriter } from './manifest-writer'
@@ -78,10 +80,50 @@ export function createVitePlugin(context: VitePluginContext): Plugin[] {
 		},
 	}
 
+	// Vite's bundled chokidar 3.6.0 fails to detect changes to .astro/data-store.json
+	// (added via watcher.add() in Astro's vite-plugin-content-virtual-mod).
+	// Without this, content collection edits update the data store on disk but the
+	// browser never receives a full-reload because Vite's watcher never fires "change"
+	// for that file. We use native fs.watch as a reliable fallback.
+	const dataStoreWatchPlugin: Plugin = {
+		name: 'cms-data-store-watch',
+		configureServer(server) {
+			if (command !== 'dev') return
+			const root = server.config.root
+			const dataStorePath = join(root, '.astro', 'data-store.json')
+			let fsWatcher: ReturnType<typeof watch> | undefined
+			let debounce: ReturnType<typeof setTimeout> | undefined
+
+			const startWatching = () => {
+				try {
+					fsWatcher = watch(dataStorePath, () => {
+						clearTimeout(debounce)
+						debounce = setTimeout(() => {
+							server.environments.client.hot.send({ type: 'full-reload', path: '*' })
+						}, 80)
+					})
+				} catch {
+					// File doesn't exist yet — retry when it appears
+					setTimeout(startWatching, 2000)
+				}
+			}
+
+			// Data store is created during content sync, which runs after server start
+			setTimeout(startWatching, 3000)
+
+			const origClose = server.close.bind(server)
+			server.close = async () => {
+				fsWatcher?.close()
+				clearTimeout(debounce)
+				return origClose()
+			}
+		},
+	}
+
 	// Note: We cannot use transformIndexHtml for static Astro builds because
 	// Astro generates HTML files directly without going through Vite's HTML pipeline.
 	// HTML processing is done in build-processor.ts after pages are generated.
 	// Source location attributes are provided natively by Astro's compiler
 	// (data-astro-source-file, data-astro-source-loc) in dev mode.
-	return [virtualManifestPlugin, watcherPlugin, createArrayTransformPlugin()]
+	return [virtualManifestPlugin, watcherPlugin, dataStoreWatchPlugin, createArrayTransformPlugin()]
 }