backpack-v42-migration

Run a discovery scan for BpkButtonV2 usage, deep imports, and autosuggest imports, then apply button changes via a migration script and migrate autosuggest files individually. Finish with typecheck and scoped test runs to verify the upgrade.

Rename BpkButtonV2 to BpkButton globally, convert named imports to default imports, and rewrite any deep src/ import paths to the public package root. A line-by-line parser is recommended over regex because most imports span multiple lines.

The legacy react-autosuggest implementation was replaced by downshift plus @floating-ui/react, making the input uncontrolled with defaultValue instead of inputProps.value. Callback signatures for onSuggestionsFetchRequested and onSuggestionSelected changed, and containerProps and top-level valid were removed.

The input freezes when inputProps.onChange or onBlur still use the v41 two-argument signature, which crashes when V2 calls them with a single React event. Wrap them in adapter functions that translate the event into the expected { newValue } shape.

V2 renders suggestions through FloatingPortal and FloatingArrow, which crash in jsdom without mocks. Mock @floating-ui/react exports and use fireEvent.click instead of element.focus() to open the suggestion menu in tests.

No, autosuggest migration cannot be fully automated because the shift from controlled to uncontrolled input changes how parent components manage state. Each wrapper component needs individual analysis, while the button migration is mechanical and scriptable.