Premium Analytics: build the internal ui and data packages as script modules

[nerrad]

Part of the work on analytics changes

Proposed changes

Why

The internal packages/* are currently bundled into every consumer: each route, widget render, and widget metadata bundle that imports one gets its own private copy. That model has three concrete failure modes, two of which we've already hit:

1. Module-scope state isn't shared across bundles. packages/data exports a module-scope QueryClient and global-error manager. Bundled per consumer, every widget type's render bundle gets its own copy — so as data-driven widget types accumulate, each carries a private cache (identical report requests across types can't dedupe) and "the" error manager fragments per bundle.
2. Styled code cannot reach style-less build contexts. Bundling resolves internal imports to raw src — including .module.scss. Any build pipeline without style plugins (concretely: the widget metadata build) hard-fails the moment its import graph touches a styled internal package (No loader is configured for ".scss" files). This is what blocks widget attribute editors today.
3. Duplicate bytes that scale with widget count. A package shared by N consumers ships N times. Tolerable at N=2; not at a dashboard of 25+ widgets.

There's no bundler-config way out of (2): esbuild honors tsconfig.json paths over package.json entry fields, so a bundled internal import always lands in src no matter what module/main point at. The only mechanism that delivers a package's compiled output to consumers is the one @wordpress/* packages already use — register it as a script module and externalize the import.

What

Declare wpScriptModuleExports on packages/ui and packages/data, so each is built once into a registered script module and consumer bundles externalize the import:

• ui — the module is built from the Phase-1 transpile output, where the CSS-module graph is already compiled via the style runtime, so styled components become consumable from any build context (first consumer: the stacked fields-package PR).
• data — the QueryClient and error manager become page-wide singletons by construction (one registered module instance, every consumer imports it), and widget metadata modules importing helpers like getDefaultQueryParams shrink from ~31 KB to ~1.5 KB each (the bundled helper/datetime slice externalizes).

Also adds the parent-manifest link: entries these modules' bundles resolve through (datetime, formatters) plus ui for future importers — the resolution mechanism documented in #49189.

Scope note: widgets-toolkit would also benefit (it bundles charts + components into every widget render) but is slated for dissolution, so it's deferred pending that decision. datetime/formatters/routing/icons are small, logic-only, and singleton-free — per-consumer bundling is fine there.

Related product discussion/links

• Mechanism documented in feat(premium-analytics): resolve internal packages for build and types #49189; first consumer lands in the stacked fields-package PR; motivating context in Premium Analytics: port the Average items per order widget #49505.

Does this pull request change what data or activity we track or use?

No.

Testing instructions

• pnpm --filter @automattic/jetpack-premium-analytics build — Phase 2 reports ✔ Bundled ui and ✔ Bundled data; build/modules/{ui,data}/ and the module registry contain the new script modules.
• pnpm --filter @automattic/jetpack-premium-analytics typecheck — clean.
• No runtime change on trunk: nothing on trunk imports these packages from built page code yet.
• Runtime-validated end to end on the experimental widget branch (try/wooa7s-1460-widget-inline-report-params-field), which carries this same config plus consumers:
  • widgets render with data/ui declared as external module dependencies, and modules/data/index.min.js loads once per page;
  • the singleton claim was validated with two different data-driven widget types (average-items-per-order and average-order-value: separate render bundles, same orders report). Test design note: instances bake concrete dates into their attributes at insert time, so both instances must be inserted the same day (identical params) for the hypotheses to separate. With identical params, a hard reload shows exactly 2 proxy/reports/orders requests (one primary + one comparison) serving both widget types — per-bundle clients would fire 4, one pair per type, with nothing deduping across bundles.

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack or WordPress.com Site Helper), and enable the update/pa-ui-script-module branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/pa-ui-script-module

bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/pa-ui-script-module

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[chihsuan]

Thanks @nerrad Clean change and looks good 👍

Just left one small optional note inline but not a blocker.