Skip to content

Conversation

@wellyshen
Copy link
Contributor

@wellyshen wellyshen commented Nov 19, 2025

A clean (non-vibe code) version of the “AI Chat” package for us to build the unified AI chat.

Proposed Changes

Why are these changes being made?

Testing Instructions

Pre-merge Checklist

  • Has the general commit checklist been followed? (PCYsg-hS-p2)
  • Have you written new tests for your changes?
  • Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
  • Have you checked for TypeScript, React or other console errors?
  • Have you tested accessibility for your changes? Ensure the feature remains usable with various user agents (e.g., browsers), interfaces (e.g., keyboard navigation), and assistive technologies (e.g., screen readers) (PCYsg-S3g-p2).
  • Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
  • Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
    • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
  • For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

@wellyshen wellyshen self-assigned this Nov 19, 2025
@github-actions
Copy link

github-actions bot commented Nov 19, 2025

@matticbot
Copy link
Contributor

matticbot commented Nov 19, 2025

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

  • blaze-dashboard
  • notifications
  • wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug add/unified-ai on your sandbox.

@wellyshen
Copy link
Contributor Author

We decided to use this PR.

@wellyshen wellyshen closed this Nov 19, 2025
@matticbot
Copy link
Contributor

matticbot commented Nov 20, 2025

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

App Entrypoints (~144 bytes added 📈 [gzipped])

name                    parsed_size           gzip_size
entry-reauth-required        +305 B  (+0.0%)     +144 B  (+0.0%)
entry-main                   +305 B  (+0.0%)     +144 B  (+0.0%)
entry-login                  +305 B  (+0.0%)     +144 B  (+0.0%)
entry-subscriptions          +144 B  (+0.0%)      +51 B  (+0.0%)
entry-stepper                +144 B  (+0.0%)      +51 B  (+0.0%)
entry-domains-landing        +144 B  (+0.0%)      +51 B  (+0.0%)
entry-dashboard-dotcom       +144 B  (+0.0%)      +51 B  (+0.0%)
entry-dashboard-ciab         +144 B  (+0.0%)      +51 B  (+0.0%)
entry-browsehappy            +144 B  (+0.1%)      +51 B  (+0.1%)

Common code that is always downloaded and parsed every time the app is loaded, no matter which route is used.

Async-loaded Components (~303 bytes added 📈 [gzipped])

name                           parsed_size         gzip_size
async-load-automattic-ai-chat       +413 B  (new)     +303 B  (new)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants