Remove optimal-components and optimal-utilities bundles

[jackgranatowski]

Summary

Removes the optimal-components and optimal-utilities pre-built CSS bundles from the distribution, along with their associated exports and documentation references.

Changes

• bundle.config.json: Removed bundle definitions for slashed.optimal-components.css, slashed.optimal-components.flat.css, slashed.optimal-utilities.css, and slashed.optimal-utilities.flat.css
• package.json: Removed package exports for ./optimal-components, ./optimal-components/flat, ./optimal-utilities, and ./optimal-utilities/flat
• Documentation: Updated README.md and docs/architecture.md to remove references to the removed bundles from the bundle table
• Configurator: Updated configurator/src/data/bundles.generated.json to reflect the removal
• Tests: Updated tests/button.spec.js and tests/card.spec.js to use the optimal bundle instead of the removed optimal-components bundle
• Demo files: Updated CDN references in demos/full-api-demo.html and demos/full-api-demo-with-overrides.html
• Generated files: Regenerated docs/api-index.json and configurator/src/data/api-index.generated.json via build process

Notes

• The optimal bundle remains as the recommended all-in-one distribution
• Tests have been updated to use the optimal bundle, which includes all necessary component styles
• All generated artifacts were updated via the standard build process

https://claude.ai/code/session_01A5nv7eHWWU2tqBjM1AHsvG

Summary by CodeRabbit

• New Features

  • The full stylesheet bundle is now the primary documented option, combining the broader set of components and utilities in one package.

• Bug Fixes

  • Demo pages and test setups were updated to load the full bundle, keeping previews and validation aligned with the latest bundle structure.
  • Package exports now reflect the available bundle options more accurately.

• Documentation

  • Updated README and architecture docs to remove retired bundle entries and describe the current bundle layout.

[qodo-code-review]

ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing

[coderabbitai]

Warning

Review limit reached

@jackgranatowski, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: c58023e4-803d-4102-ae1b-064e7a5d3d8b

📥 Commits

Reviewing files that changed from the base of the PR and between 69b7eb6 and 51ea1f8.

📒 Files selected for processing (13)

• README.md
• bundle.config.json
• configurator/src/data/api-index.generated.json
• configurator/src/data/bundles.generated.json
• demos/full-api-demo-with-overrides.html
• demos/full-api-demo.html
• demos/generate.mjs
• docs/api-index.json
• docs/architecture.md
• package.json
• scripts/gen-api-index.js
• tests/button.spec.js
• tests/card.spec.js

📝 Walkthrough

Walkthrough

Removes the optimal-components and optimal-utilities CSS bundle tiers across bundle configuration, generated manifest, and package exports. Updates README, architecture docs, API index schema text, demo pages/generator, and Playwright tests to reference slashed.full.css instead.

Changes

Bundle Tier Removal

Layer / File(s)	Summary
Bundle configuration and manifest updates bundle.config.json, configurator/src/data/bundles.generated.json, package.json	Removes optimal-components/optimal-utilities bundle output definitions and their .flat variants from the config, trims corresponding entries and optionalModules from the generated manifest, and removes matching exports subpaths from package.json.
Docs and API index schema updates README.md, docs/architecture.md, scripts/gen-api-index.js	Updates the bundle documentation table and generated schema description to drop the retired tiers and describe slashed.full.css composition.
Demo pages and generator updated to full bundle demos/full-api-demo.html, demos/full-api-demo-with-overrides.html, demos/generate.mjs	Switches stylesheet links and generator CDN constant to slashed.full.css, and updates banner/version text from “optimal-components bundle” to “full bundle”.
Playwright tests updated to full bundle tests/button.spec.js, tests/card.spec.js	Updates COMPONENTS_BUNDLE to dist/slashed.full.css and adds a comment noting the retirement of the optimal-components tier.

Estimated code review effort: 2 (Simple) | ~12 minutes

Possibly related PRs

• codeslash-dev/SLASHED#55: Both PRs modify bundle tiering/manifests around optimal-components/optimal-utilities in bundle.config.json and related docs.
• codeslash-dev/SLASHED#60: Both PRs touch the same bundle tier artifacts/exports for optimal-components/optimal-utilities flat variants.
• codeslash-dev/SLASHED#454: Both PRs modify demos/generate.mjs and full-api-demo* HTML to load a different stylesheet bundle tier.

Suggested labels: codex

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: removing the optimal-components and optimal-utilities bundles.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/wp-plugin-version-selection-2d9jki

Warning

Review ran into problems

🔥 Problems

Git: Failed to clone repository. Please run the @coderabbitai full review command to re-trigger a full review. If the issue persists, set path_filters to include or exclude specific files.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}