@imwz/wp-pattern-sentinel 1.0.2 → 1.0.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@imwz/wp-pattern-sentinel",
-  "version": "1.0.2",
+  "version": "1.0.4",
   "description": "Browser-based WordPress block pattern validator using Playwright",
   "type": "module",
   "engines": {
@@ -25,6 +25,10 @@
     "validation"
   ],
   "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/imagewize/wp-pattern-sentinel"
+  },
   "dependencies": {
     "js-yaml": "^4.1.0",
     "p-queue": "^8.0.1",

package/src/editor.js

@@ -29,10 +29,11 @@ function stripPhpForValidation(content) {
 }
 
 /**
- * Strip the PHP file header (opening tag + docblock) and return the raw block markup.
- * Inline PHP expressions within the block markup are replaced with static values
- * so the editor receives valid content for round-trip validation.
- * Returns null if no block comment is found.
+ * Strip the PHP file header (opening tag, docblock, and any header-only PHP
+ * such as a direct-access guard) and return the raw block markup. Inline PHP
+ * expressions within the block markup are replaced with static values so the
+ * editor receives valid content for round-trip validation. Returns null if no
+ * block comment is found.
  *
  * WordPress pattern files look like:
  *   <?php
@@ -40,14 +41,20 @@ function stripPhpForValidation(content) {
  *    * Title: My Pattern
  *    * ...
  *    *\/
+ *
+ *   if ( ! defined( 'ABSPATH' ) ) {
+ *       exit; // Optional direct-access guard (e.g. Aludra patterns).
+ *   }
  *   ?>
  *   <!-- wp:group -->...
+ *
+ * The header is everything up to and including the *first* closing PHP tag,
+ * regardless of what it contains (docblock only, or docblock + guard) — so a
+ * single non-greedy strip handles both shapes in one pass.
  */
 export function extractBlockContent(fileContent) {
   const stripped = fileContent
-    .replace(/^<\?php\s*/m, '')
-    .replace(/\/\*\*[\s\S]*?\*\//m, '')
-    .replace(/^\s*\?>\s*/m, '')
+    .replace(/^[\s\S]*?\?>\s*/, '')
     .trim();
 
   if (!stripped.startsWith('<!--')) return null;

package/src/validation.js

@@ -76,9 +76,19 @@ const normalizeBlockAttrJson = str => {
   });
 };
 
+/**
+ * Collapse whitespace (including newlines) between adjacent tags/comments to
+ * nothing. Custom blocks that render their wrapper markup via JSX (e.g.
+ * `<div><div className="inner">...`) serialize with zero whitespace between
+ * elements, while hand-authored pattern PHP conventionally puts each nested
+ * element on its own line for readability. That's insignificant whitespace —
+ * browsers treat it identically — so it must not produce a content_mismatch.
+ */
+const collapseInterTagWhitespace = str => str.replace(/>\s+</g, '><');
+
 /** Apply all WordPress serializer normalizations to both sides before diffing. */
 const normalizeForComparison = str =>
-  normalizeBlockAttrJson(normalizeCssProps(stripNavRef(str)));
+  collapseInterTagWhitespace(normalizeBlockAttrJson(normalizeCssProps(stripNavRef(str))));
 
 /**
  * Compare the editor's serialized output against the original source.