Production Checklist

Use this checklist before publishing a new EnterUI version or adopting it in a public product surface.

#Package Checks

• @froggdesign/enter-ui exports only documented public entry points.
• @froggdesign/enter-ui/styles.css is included in the published package.
• React and React DOM remain peer dependencies.
• App-only docs files are not included in the npm package.
• sideEffects keeps CSS imports from being tree-shaken.
• npm pack --dry-run lists only expected package files.

#Verification Commands

pnpm exec biome check packages/enterui-react apps/enterui-web
pnpm --filter @froggdesign/enter-ui typecheck
pnpm --filter @froggdesign/enter-ui test
pnpm --filter @froggdesign/enter-ui build
pnpm --filter enterui-web typecheck
pnpm --filter enterui-web build
pnpm --filter @froggdesign/enter-ui exec npm pack --dry-run

#Accessibility Checks

• Every icon-only action has an accessible name.
• Dialogs have titles and descriptions.
• Form controls have labels and error/help text wired through ARIA.
• Menus, selects, tabs, accordions, popovers, tooltips, and toasts can be used with keyboard and pointer input.
• Disabled, invalid, selected, checked, current, and loading states are exposed semantically.

#Release Notes

Use Changesets for public package changes. Patch releases should be limited to bug fixes, documentation, tests, and additive non-breaking behavior. Minor releases may add components or props. Major releases are required for breaking contract changes.