Add/forms field icon rasterizer by CGastrell · Pull Request #46979 · Automattic/jetpack

CGastrell · 2026-02-05T16:41:45Z

Proposed changes:

Adds a complete pipeline to extract and rasterize block field icons for use in email templates.

Icon extraction (`pnpm extract-icons`)

Renders React icon components (src/blocks/field-*/icon.{jsx,tsx}) to standalone SVG files via webpack + ReactDOMServer. Handles all icon patterns:

Inline @wordpress/primitives — SVG/Path/Circle/Line components (14 icons)
@wordpress/icons via <Icon> wrapper — Bypasses the Icon wrapper by extracting the inner element from props (3 icons)
Direct @wordpress/icons reference — Resolves the .src property (1 icon)
Direct element export — Used as-is (1 icon)

Post-processing normalizes the SVG output:

Unwraps nested <svg> elements (fixes prior branch's rating icon bug)
Ensures xmlns, width, height, aria-hidden, focusable attributes
Converts empty element pairs to self-closing tags
Formats with basic indentation

Mocks @wordpress/components during extraction to avoid needing jsdom.

Icon rasterization (`pnpm rasterize-icons`)

Replaces currentColor with #000 on the fly for standalone rendering
Converts each icon.svg to a 48x48 retina PNG (field-*@2x.png) with ~~white background~~ using sharp. Output goes to src/contact-form/images/field-icons/ for use by the email template renderer.

Combined pipeline

pnpm generate-icons runs both steps in sequence.

Other information:

Have you written new tests for your changes, if applicable?
Have you checked the E2E test CI results, and verified that your changes do not break them?
Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

None

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

No

Testing instructions:

Clean test (from scratch)

From projects/packages/forms/:

# Remove all generated icon files to start fresh
rm -f src/blocks/field-*/icon.svg
rm -rf src/contact-form/images/field-icons/

# Run the full pipeline
pnpm generate-icons

# Verify SVG files were created (19 expected)
ls src/blocks/field-*/icon.svg | wc -l

# Verify PNG files were created (19 expected)
ls src/contact-form/images/field-icons/*.png | wc -l

Verify individual steps

# Extract only (React → SVG)
rm -f src/blocks/field-*/icon.svg
pnpm extract-icons
# Check output: 19 SVG files, no nested <svg>, no currentColor

# Rasterize only (SVG → PNG)
rm -rf src/contact-form/images/field-icons/
pnpm rasterize-icons
# Check output: 19 PNG files in src/contact-form/images/field-icons/, 48x48px, white background

Visual verification

Open a few PNGs to confirm they render correctly:

src/contact-form/images/field-icons/field-email@2x.png — envelope icon
src/contact-form/images/field-icons/field-rating@2x.png — three stars (no nested SVG artifacts)
src/contact-form/images/field-icons/field-slider@2x.png — slider line with dot (black, not invisible)
src/contact-form/images/field-icons/field-hidden@2x.png — crossed-out eye icon

github-actions · 2026-02-05T16:42:42Z

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 add/forms-field-icon-rasterizer branch.
To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack add/forms-field-icon-rasterizer

bin/jetpack-downloader test jetpack-mu-wpcom-plugin add/forms-field-icon-rasterizer

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 · 2026-02-05T16:42:54Z

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:

Ensure all required checks appearing at the bottom of this PR are passing.
Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
You can use GitHub's Reviewers functionality to request a review.
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!

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
WoA releases happen weekly.
Releases to self-hosted sites happen monthly:
- Scheduled release: March 3, 2026
- Code freeze: March 3, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

Copilot

Pull request overview

This PR adds tooling to rasterize SVG block icons to JPG format for use in email templates and dashboards. The implementation includes a Node.js script that processes field block icons and generates 48x48 pixel retina-ready JPG images with white backgrounds.

Changes:

Added rasterize-icons.mjs script to convert SVG icons to JPG format
Generated JPG files for all 19 field block icons
Added sharp dependency for image processing

Reviewed changes

Copilot reviewed 5 out of 25 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
projects/packages/forms/tools/rasterize-icons.mjs	New script that finds and converts SVG icons to JPG format with appropriate error handling
projects/packages/forms/src/blocks/field-*/icon@2x.jpg	Generated JPG files (19 total) for all field blocks
projects/packages/forms/package.json	Added `sharp` dependency and `rasterize-icons` npm script
pnpm-workspace.yaml	Configured to allow building sharp native dependencies
pnpm-lock.yaml	Updated with sharp and its platform-specific dependencies
projects/packages/forms/README.md	Documented the rasterization process and usage
projects/packages/forms/changelog/add-forms-field-icon-rasterizer	Added changelog entry following project conventions

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

jp-launch-control · 2026-02-05T17:01:02Z

Code Coverage Summary

Cannot generate coverage summary while tests are failing. 🤐

Please fix the tests, or re-run the Code coverage job if it was something being flaky.

Full summary · PHP report · JS report

_{Coverage check overridden by

Coverage tests to be added later
Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR
.}

Copilot

Pull request overview

Copilot reviewed 9 out of 31 changed files in this pull request and generated 5 comments.

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

projects/packages/forms/tools/rasterize-icons.mjs

projects/packages/forms/README.md

projects/packages/forms/tools/extract-icons.mjs

simison · 2026-02-06T09:37:33Z

Added Triforce as a reviewer because we're touching build tooling here.

simison · 2026-02-06T09:40:26Z

with white background using sharp

For emails that can be rendered in dark mode, it would be better if they were with a transparent background.

simison · 2026-02-06T09:42:24Z

projects/packages/forms/tools/rasterize-icons.mjs

+const __dirname = dirname( fileURLToPath( import.meta.url ) );
+const formsRoot = join( __dirname, '..' );
+const blocksDir = join( formsRoot, 'src', 'blocks' );
+const outputDir = join( formsRoot, 'src', 'contact-form', 'images', 'field-icons' );
+


Feels like these folder and file matching specifics should be handled by the webpack config, not the script.

Might be the case, but it's also true it's not likely the directory structure will be changing. And if it does, it will be easy to change the script. The final location is also still waiting for the final decision on where the images should be for public access (we're defining this on the email template step, still in process).

That said, why not? :) ef97b44

simison · 2026-02-06T09:42:58Z

projects/packages/forms/tools/extract-icons.mjs

+const __dirname = dirname( fileURLToPath( import.meta.url ) );
+const formsRoot = join( __dirname, '..' );
+const blocksDir = join( formsRoot, 'src', 'blocks' );
+
+// ---------------------------------------------------------------------------
+// Step 1: Discover icon files
+// ---------------------------------------------------------------------------
+
+const ICON_EXTENSIONS = [ 'icon.jsx', 'icon.tsx', 'icon.js' ];


Same comment as here https://github.com/Automattic/jetpack/pull/46979/changes#r2773196270 — I'd expect the file rules from Webpack config, not here.

Attempting to address both comments on ef97b44

simison · 2026-02-06T09:46:14Z

projects/packages/forms/tools/extract-icons.mjs

+	}
+
+	// Replace currentColor with black (won't render in standalone SVG/email)
+	svg = svg.replace( /currentColor/g, '#000' );


Wouldn't sites' frontend still need svg's with currentColor?

Good point, yes, we need to refine a couple things but likely this was not needed.

Moved it to the rasterizer script. The measure is a failsafe as well, most of our icons don't actually use a value for the color (not even currentColor), they rely on CSS for it. There are a couple exceptions but a single one using fixed #000, changing that to currentColor on a separate PR.

80ecadd

manzoorwanijk

This looks fine to me. Apart from inline comments, I wonder whether there should be a CI step to generate those icons to ensure that they are not stale as they are generated on demand.

manzoorwanijk · 2026-02-06T10:08:20Z

projects/packages/forms/tools/rasterize-icons.mjs

+			await sharp( svgFile, { density: 96 } )
+				.resize( 48, 48 )


I have used Sharp before, so I know a little bit about it. 😄

Sharp's density controls how SVG units map to pixels. With all icons being 24x24 viewBox and density 96, sharp rasterizes them at 24 × (96/72) = 32px, then upscales to 48px. This produces blurry output.

To get native 48px rendering (no upscale), the density should be 144 (since 24 × 144/72 = 48). With density: 144, you won't need .resize(48, 48).

Suggested change

await sharp( svgFile, { density: 96 } )

.resize( 48, 48 )

await sharp( svgFile, { density: 144 } )

This may not sound a great improvement for images as this small, but for larger images it makes a considerable difference.

TIL! Not at all a user of sharp, this setup is mostly Claudo magic, but good to know! 75978c2

manzoorwanijk · 2026-02-06T10:10:42Z

projects/packages/forms/tools/extract-icons.mjs

+ */
+function postProcessSvg( svg ) {
+	// Unwrap nested <svg> — take the inner one
+	const nestedMatch = svg.match( /^<svg[^>]*>\s*(<svg[\s\S]*<\/svg>)\s*<\/svg>$/ );


This regex is too brittle/fragile for me. Maybe add comments about what we expect here?

Why not use a DOM parser (like htmlparser2, which is lightweight) instead of a regex? That would make transformation predictable and testable.

Added a comment, since svg files are machine generated adding a dependency (even as light as htmlparser2) feels a bit too much? Let me know if you have a strong opinion on this, I can add the parser if it seems safer.

manzoorwanijk · 2026-02-06T10:12:02Z

projects/packages/forms/tools/extract-icons.mjs

+
+	// Ensure xmlns
+	if ( ! svg.includes( 'xmlns=' ) ) {
+		svg = svg.replace( '<svg ', '<svg xmlns="http://www.w3.org/2000/svg" ' );


How does this work for avgs without attributes - <svg> or are we sure we always have attributes?

The target is not generic, the svg files are specific to wordpress/icons and those custom we crafted. Maybe it needs more grooming but we're not aiming (nor planning to) this to be a solution that mangles anything thrown at, just our specific set of icons. These might get new ones, though it's not something we expect to change/add too often. I'll look into it, but most icons are from a controlled source.

manzoorwanijk · 2026-02-06T10:16:00Z

projects/packages/forms/tools/extract-icons.mjs

+		if ( ! svgTag.includes( 'viewBox=' ) ) {
+			throw new Error( 'SVG is missing a viewBox attribute; cannot infer width/height.' );
+		}
+		svg = svg.replace( /viewBox=/, 'width="24" height="24" viewBox=' );


Maybe detect the size from the viewBox?

manzoorwanijk · 2026-02-06T10:26:09Z

projects/packages/forms/tools/extract-icons.mjs

+// ---------------------------------------------------------------------------
+
+try {
+	unlinkSync( runnerPath );


If Step 3, 4, or 5 fails, this clean-up never happens, right? Maybe wrap them in try/catch?

manzoorwanijk · 2026-02-06T10:32:50Z

projects/packages/forms/tools/extract-icons.mjs

+const require_ = createRequire( import.meta.url );
+const bundlePath = join( formsRoot, 'dist', 'extract-icons-bundle.cjs' );
+const bundleExport = require_( bundlePath );
+const icons = bundleExport.default || bundleExport;


Maybe add a check to count the icons created to ensure that we didn't miss any?

Maybe, but should we harcode that? Can you elaborate on this?

CGastrell · 2026-02-08T15:40:29Z

with white background using sharp

For emails that can be rendered in dark mode, it would be better if they were with a transparent background.

The idea that popped up when we discussed this concern was to forcibly add a white background on the template. The reason being we need to use raster images due to lack of SVG support on all clients and those won't adapt to light/dark schemes, even with transparency (black fills with transparent bg over a dark surface).

That said, this PR is mostly to bring up all the concerns and constraints and come up with the best approach.

For example, we need to test if this would work on all email clients:

@media (prefers-color-scheme: dark) {
  img {
    filter: invert(1);
  }
}

Copilot

Pull request overview

Copilot reviewed 9 out of 31 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

Copilot · 2026-02-09T02:31:06Z

projects/packages/forms/README.md

+1. **`extract-icons`** — Renders each React icon component to static SVG markup and writes `icon.svg` files.
+2. **`rasterize-icons`** — Converts each `icon.svg` to a 48x48 retina PNG (`icon@2x.png`) with a white background, optimized for minimal file size.
+
+Run the full pipeline:
+
+```bash
+pnpm generate-icons
+```
+
+Or run each step individually:
+
+```bash
+pnpm extract-icons     # React components → icon.svg
+pnpm rasterize-icons   # icon.svg → icon@2x.png
+```


README documents rasterize output as icon@2x.png, but tools/rasterize-icons.mjs actually writes ${blockName}@2x.png (e.g., field-email@2x.png) into src/contact-form/images/field-icons/. Please update the filename examples/comments here so they match the script output to avoid confusion when running the pipeline.

projects/packages/forms/changelog/add-forms-field-icon-rasterizer

Copilot

Pull request overview

Copilot reviewed 9 out of 31 changed files in this pull request and generated 1 comment.

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

projects/packages/forms/tools/extract-icons.mjs

CGastrell · 2026-02-09T03:18:04Z

This looks fine to me. Apart from inline comments, I wonder whether there should be a CI step to generate those icons to ensure that they are not stale as they are generated on demand.

Possibly? Not yet though. This was thought to be a manual run since we don't usually change the icons that much. But there are still some open questions we need to go through. Right now, I think a manual generation is enough. Whenever we're changing an icon (likely on js/jsx/tsx) what I'd like to have is a watch that would trigger the generation (only when those icon files change). This way, once we're done changing whatever icon, the diff will show both a .svg and a .png file to be committed. Good for follow up though.

Adds a Node.js script that converts SVG block icons (src/blocks/field-*/icon.svg) into 48x48 JPG files with white background for use in email templates. The output is named icon@2x.jpg (2x retina for 24x24 display). Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Adds sharp as a devDependency for the rasterize-icons script and approves its build scripts in pnpm-workspace.yaml. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

First batch of 48x48 retina JPG icons generated from SVG sources using the rasterize-icons script. These are used in form notification email templates. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Renders React icon components to standalone SVG files via webpack + ReactDOMServer. Handles all icon patterns: inline @wordpress/primitives, @wordpress/icons via <Icon> wrapper, and direct icon references. Mocks @wordpress/components to avoid jsdom — the Icon wrapper is bypassed by extracting the inner element from props. Post-processing fixes: nested <svg> unwrapping, currentColor replacement with #000 for email rendering, attribute normalization. Adds `pnpm generate-icons` to run the full pipeline (extract + rasterize). Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Re-extracts icon.svg files using the new extract-icons script. - field-hidden: minor attribute reordering from @wordpress/icons source - field-slider: currentColor replaced with #000 for email template use Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Output PNGs to a centralized directory alongside the email template assets rather than scattering them across individual block directories. Updates README to fix lingering JPG→PNG reference. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Throw an explicit error if a rendered SVG is missing a viewBox attribute, since width/height injection depends on it. Without this guard the replacement silently fails and produces icons without dimensions. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

…tsWith iterator

…ould produce noticeably crisper output

…cons-runner.js file gets cleaned up even if webpack, bundle execution, or SVG writing fails

Copilot

Pull request overview

Copilot reviewed 9 out of 32 changed files in this pull request and generated 2 comments.

Files not reviewed (1)

pnpm-lock.yaml: Language not supported

projects/packages/forms/tools/extract-icons.mjs

Copilot · 2026-02-09T03:29:43Z

projects/packages/forms/tools/extract-icons.mjs

+/**
+ * Extract SVG icons from React icon components.
+ *
+ * Discovers all icon.{jsx,tsx} files in src/blocks/field-* directories,


The header comment says the script discovers icon.{jsx,tsx} files, but iconPipelineConfig.iconFilenames also includes icon.js. Update the comment (or the config) so the supported extensions are accurately documented.

Suggested change

* Discovers all icon.{jsx,tsx} files in src/blocks/field-* directories,

* Discovers all icon.{js,jsx,tsx} files in src/blocks/field-* directories,

CGastrell · 2026-02-09T03:42:36Z

with white background using sharp

For emails that can be rendered in dark mode, it would be better if they were with a transparent background.

@simison 1d78c5f

CGastrell self-assigned this Feb 5, 2026

Copilot AI review requested due to automatic review settings February 5, 2026 16:41

CGastrell added [Status] In Progress [Type] Task [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Package] Forms Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR labels Feb 5, 2026

Copilot started reviewing on behalf of CGastrell February 5, 2026 16:42 View session

github-actions bot added [Block] Contact Form Form block (also see Contact Form label) [Feature] Contact Form Docs labels Feb 5, 2026

Copilot AI reviewed Feb 5, 2026

View reviewed changes

CGastrell added [Status] Needs Review This PR is ready for review. and removed [Status] In Progress labels Feb 5, 2026

Copilot AI review requested due to automatic review settings February 5, 2026 20:18

Copilot started reviewing on behalf of CGastrell February 5, 2026 20:18 View session

Copilot AI reviewed Feb 5, 2026

View reviewed changes

simison requested review from a team February 6, 2026 09:37

simison reviewed Feb 6, 2026

View reviewed changes

manzoorwanijk reviewed Feb 6, 2026

View reviewed changes

Copilot AI review requested due to automatic review settings February 9, 2026 02:26

Copilot started reviewing on behalf of CGastrell February 9, 2026 02:26 View session

Copilot AI reviewed Feb 9, 2026

View reviewed changes

Copilot AI review requested due to automatic review settings February 9, 2026 02:53

Copilot started reviewing on behalf of CGastrell February 9, 2026 02:53 View session

Copilot AI reviewed Feb 9, 2026

View reviewed changes

projects/packages/forms/tools/extract-icons.mjs Outdated Show resolved Hide resolved

CGastrell and others added 17 commits February 9, 2026 00:22

Forms: add sharp dependency for icon rasterization

a69865d

Adds sharp as a devDependency for the rasterize-icons script and approves its build scripts in pnpm-workspace.yaml. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Forms: add rasterized block field icons for email templates

be97708

First batch of 48x48 retina JPG icons generated from SVG sources using the rasterize-icons script. These are used in form notification email templates. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Forms: add changelog for icon rasterizer

8188877

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Forms: update changelog for icon pipeline

13c4dee

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

rasterize to png instead of jpg

1da90d0

move/create settings on webpack config file, use glob instead of star…

baf3d44

…tsWith iterator

convert currentColor to #000 on the fly before rasterizing to PNG

36814cc

PNGs now rendered natively at 48px instead of upscaled from 32px — sh…

7a1fca9

…ould produce noticeably crisper output

harden regex for xmlns insertion

0841031

width/height — parsed from viewBox dimensions instead of hardcoded 24

4ffb935

add comment regarding nested svgs

5765dd5

Steps 3–5 are now wrapped in try/finally, so the temporary .extract-i…

a0cc5d8

…cons-runner.js file gets cleaned up even if webpack, bundle execution, or SVG writing fails

Copilot AI review requested due to automatic review settings February 9, 2026 03:23

CGastrell force-pushed the add/forms-field-icon-rasterizer branch from 59eb271 to a0cc5d8 Compare February 9, 2026 03:23

Copilot started reviewing on behalf of CGastrell February 9, 2026 03:23 View session

produce transparent pngs

1d78c5f

Copilot AI reviewed Feb 9, 2026

View reviewed changes

update readme

838b3f0

	await sharp( svgFile, { density: 96 } )
	.resize( 48, 48 )
	await sharp( svgFile, { density: 144 } )

	* Discovers all icon.{jsx,tsx} files in src/blocks/field-* directories,
	* Discovers all icon.{js,jsx,tsx} files in src/blocks/field-* directories,

Conversation

CGastrell commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Proposed changes:

Icon extraction (pnpm extract-icons)

Icon rasterization (pnpm rasterize-icons)

Combined pipeline

Other information:

Jetpack product discussion

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

Testing instructions:

Clean test (from scratch)

Verify individual steps

Visual verification

Uh oh!

github-actions bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions bot commented Feb 5, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

jp-launch-control bot commented Feb 5, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Code Coverage Summary

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

simison commented Feb 6, 2026

Uh oh!

simison commented Feb 6, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CGastrell Feb 9, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

manzoorwanijk left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

CGastrell Feb 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

CGastrell commented Feb 5, 2026 •

edited

Loading

Icon extraction (`pnpm extract-icons`)

Icon rasterization (`pnpm rasterize-icons`)

github-actions bot commented Feb 5, 2026 •

edited

Loading

jp-launch-control bot commented Feb 5, 2026 •

edited

Loading

CGastrell Feb 9, 2026 •

edited

Loading

CGastrell Feb 8, 2026 •

edited

Loading