@10up/wp-vite-plugins 1.0.0-alpha.0 → 1.0.0-alpha.1

package/dist/index.d.ts

@@ -174,7 +174,36 @@ interface WpExternalsOptions {
      * Example: `['ignite-wp-navigation', 'ignite-*']`
      */
     scriptModuleNamespaces?: string[];
+    /**
+     * Bare package names to **force-bundle**: their externalization is
+     * suppressed and their imports are rewritten to resolve against the
+     * installed package's ESM entry instead.
+     *
+     * The escape hatch for packages whose WP metadata does not match what
+     * WordPress core actually registers. Merges with (never replaces)
+     * `DEFAULT_BUNDLED_PACKAGES`.
+     *
+     * Bare names only — `@wordpress/dataviews/wp` and other subpath entries
+     * throw at config time, because force-bundling is a whole-package verdict.
+     *
+     * Example: `['@wordpress/icons', 'some-lying-package']`
+     */
+    bundle?: string[];
 }
+/**
+ * Packages that claim externalizability they don't have. Same rationale as
+ * core's `dependency-extraction-webpack-plugin` keeping a hardcoded
+ * `BUNDLED_PACKAGES` list: the metadata is wrong with respect to what core
+ * registers, and there is nowhere else to record that.
+ *
+ * `@wordpress/icons@10.x` ships `wpScript: true`, but WordPress core registers
+ * no `wp-icons` script — it's absent from `script-loader-packages.php`. Trusting
+ * the metadata produces two failures at once: `window.wp.icons` is undefined,
+ * *and* the unregistered `wp-icons` dependency makes WordPress refuse to
+ * enqueue the script at all. (`@wordpress/icons@11.x` dropped `wpScript`, so
+ * without this list the behavior depends on which copy the resolver hoists.)
+ */
+declare const DEFAULT_BUNDLED_PACKAGES: string[];
 declare function wpExternals(options?: WpExternalsOptions): Plugin[];
 
 interface WpOptions {
@@ -195,11 +224,21 @@ interface WpOptions {
     externals?: WpExternalsOptions | false;
     /** Disable the auto-included script-IIFE helper. Default: enabled in script mode. */
     iife?: false;
+    /**
+     * Disable the auto-included per-entry module duplication. Default: enabled
+     * in script mode. Without it, a module two script entries share becomes a
+     * shared chunk each entry `import`s — invalid as a classic script.
+     */
+    scriptDedupe?: false;
     /** Disable the auto-included CSS-only-chunk cleanup. Default: always enabled. */
     cleanCssChunks?: false;
+    /** Disable the auto-included CSS-only-entry `.asset.php` sidecars. Default: always enabled. */
+    cssAssetInfo?: false;
 }
 declare function wp(options?: WpOptions): Plugin[];
 
+declare function wpScriptDedupe(): Plugin;
+
 /**
  * vite-plugin-wp-script-iife
  *
@@ -208,6 +247,15 @@ declare function wp(options?: WpOptions): Plugin[];
  * bodies, defeating the global-scope isolation needed when WP enqueues
  * these as classic <script> tags.
  *
+ * It is also the gate that guarantees the output *is* a valid classic script:
+ * every chunk is parsed before it's wrapped, and one that doesn't compile fails
+ * the build instead of shipping a file the browser cannot load. The two causes
+ * worth diagnosing by name are a live `import`/`export` statement (a shared
+ * chunk Rolldown refused to duplicate) and an `import.meta` reference (Vite's
+ * dynamic-import preload helper). The `import.meta` members that helper touches
+ * are rewritten to classic-script-safe expressions through an injected
+ * `define`, so the failure only fires for cases the define can't reach.
+ *
  * Only run this in script mode. Module-mode entries (`wp_register_script_module`)
  * must stay as bare ESM for WP's import map to resolve them at runtime.
  */
@@ -228,4 +276,6 @@ declare function wpScriptIife(): Plugin;
 
 declare function wpCleanCssChunks(): Plugin;
 
-export { type ExternalNamespace, type WpAdminPagesOptions, type WpAdminPagesPhpOptions, type WpBlockStylesOptions, type WpBlocksOptions, type WpCopyAssetsOptions, type WpExternalsOptions, type WpOptions, wp, wpAdminPages, wpBlockStyles, wpBlocks, wpCleanCssChunks, wpCopyAssets, wpExternals, wpScriptIife };
+declare function wpCssAssetInfo(): Plugin;
+
+export { DEFAULT_BUNDLED_PACKAGES, type ExternalNamespace, type WpAdminPagesOptions, type WpAdminPagesPhpOptions, type WpBlockStylesOptions, type WpBlocksOptions, type WpCopyAssetsOptions, type WpExternalsOptions, type WpOptions, wp, wpAdminPages, wpBlockStyles, wpBlocks, wpCleanCssChunks, wpCopyAssets, wpCssAssetInfo, wpExternals, wpScriptDedupe, wpScriptIife };