[retrofox]

Part of WOOA7S-2174 (task D4).

Builds on #53778, now on trunk.

Proposed changes

Fifty-seven widgets ship without a widget.ts

Their module exported {}, or attributes: [] with an empty example, which is what the dashboard builds from the record alone: useWidgetTypes has a branch for a record without widget_module, wp-build marks the folder has_widget: false, the generated manifest leaves widget_module null, and the i18n lane skips the metadata bundle while still installing the render catalog.

Twenty-nine Premium Analytics widgets and twenty-eight WooCommerce Stats widgets lose their module. The 23 that keep one carry either attribute behavior JSON cannot express (computed elements or values, a helper-built field) or an example, which the build does not read from widget.json yet. Their static attributes move to widget.json in a follow-up.

The attribute type moves into render.tsx

render.tsx imported the widget's own shape from the module and composed the render-only type over it. Without a module, the shape is declared, and exported, in render.tsx, where stories and tests import it. All-time stats takes its metrics table along; the render catalog is installed before the module imports, so the labels translate as before.

Stories pass the manifest alone

createStoryWidgetType() takes the module as an optional second argument; the 28 stories of widgets without one drop the import. The all-time stats suite loses the test that asserted the module's empty attribute list.

Docs

.agents/rules/widgets.md and AGENTS.md state the split: an attribute is declared in widget.json whenever its field is static, and widget.ts carries only what JSON cannot express, plus example until it can move too. They describe widget.ts as optional and say where the attribute type lives in each case.

Not in this PR: the 18 modules whose example seeds inserted instances (chartType: 'bar', metric: 'opens', …) stay until example can be declared in widget.json.

Related product discussion/links

• Linear: WOOA7S-2174

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

No.

Testing instructions

Build with dependencies

jetpack build --deps packages/premium-analytics

jetpack build packages/woocommerce-stats

GET /wp-json/wpcom/v2/widget-modules

The 57 records carry widget_module: null and keep their attributes, title and icon.

On the dashboard

Every section renders as before, and the inserter offers the same widgets with the same titles and icons. The WooCommerce chart widgets keep their line/bar toggle, whose attribute lives in widget.json.

Storybook

The WidgetDashboardWithWidget story of a widget without a module (Tags, Referrers, Total views, …) renders the widget inside the dashboard.

Tests

pnpm run test --testPathPatterns=tests/groups/widgets- in projects/packages/premium-analytics, and pnpm run test in projects/packages/woocommerce-stats.

[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), and enable the refactor/record-only-widgets branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack refactor/record-only-widgets

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

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/premium-analytics/widgets/all-time-stats/render.tsx	9/9 (100.00%)	0.00%	0 💚

Full summary · PHP report · JS report

[louwie17]

Thanks @retrofox, this tested well and code looks good! I checked all the tabs and the inserter on my local Docker site, plus the line/bar toggle on the Woo chart widgets, and everything rendered the same as before.

I did leave two small inline comments on the docs, neither is a blocker and both can be a quick fix before merging or a follow up. LGTM 🚀

[louwie17]

A small nitpick, none of the stories or tests import these types right now, they all only import the default component. Maybe we can drop the "where stories and tests import it" part, or drop the export on the types until something needs them?

[retrofox]

Right, nothing imports them yet. Dropped the claim and kept the export: a type export costs nothing and keeps the name reachable for a story or test. Pushed to #53840 (4aebf0a) so this diff stays as reviewed.