Add an integration test suite

[csandman]

Summary

Adds the package's first real integration test suite, built on top of the upstream react-select tests with adaptations for the Chakra wrapper. Before this PR the only tests were in codemod/; the package itself had zero coverage.

What's in here

Ported from react-select@5.10.2 — the core component tests come straight from upstream, adapted only where chakra-react-select diverges. Each ported file carries a header comment with a permalink to its source at the pinned version:

• src/tests/select.test.tsx ← Select.test.tsx
• src/tests/async-select.test.tsx ← Async.test.tsx
• src/tests/creatable-select.test.tsx ← Creatable.test.tsx
• src/tests/async-creatable-select.test.tsx ← AsyncCreatable.test.tsx
• src/tests/state-managed-select.test.tsx ← StateManaged.test.tsx
• src/tests/constants.ts ← constants.ts (verbatim — option fixtures)

Adaptations applied to every ported file (also documented in CONTRIBUTING.md for future dep bumps):

• Imports point at ../index instead of ../Select/etc.
• A Chakra-provider-wrapped render (see src/tests/render.tsx) replaces the bare @testing-library/react render.
• userEvent.setup() + await user.X(...) instead of synchronous userEvent.X(...) (the upstream tests predate userEvent v14's async API).
• vi.fn/vi.mock instead of jest.fn/jest.mock.
• A small src/tests/cases.ts shim provides the jest-in-case cases() function (with per-case skip/only flag support) so the upstream parameterised tests run unchanged.
• Snapshot tests dropped — Chakra renders a different DOM than upstream's emotion-styled components, so the snapshots would lock us to whatever the test happened to render first.
• A handful of tests are test.skiped with oxlint-disable-next-line comments: either upstream's own QUESTION-marked tests (e.g. "we currently do not do this, do we want to?") or intentional Chakra divergences (the theme prop is intentionally ignored in favor of Chakra's design tokens).

Chakra-specific tests — src/tests/chakra-specific.test.tsx covers the props this package adds on top of react-select: size, variant, invalid, disabled, readOnly, chakraStyles, tagColorPalette, tagVariant, selectedOptionStyle, selectedOptionColorPalette, focusRingColor, plus the useChakraSelectProps hook. Uses a "probe pattern" — pass a chakraStyles callback that captures state.selectProps.<prop> — to verify wiring without depending on jsdom's CSS engine (which can't reliably parse Chakra's @layer-based CSS).

One incidental fix — in src/use-chakra-select-props.ts, passing invalid directly to <Select> now propagates to aria-invalid on the input. Previously only <Field.Root invalid> did. Surfaced while writing the chakra-specific tests.

Infrastructure

• Test runner: Vitest + jsdom + @testing-library/react + @testing-library/user-event + @testing-library/jest-dom (matches the codemod's already-vitest setup).
• src/tests/setup.ts wires up cleanup, a matchMedia polyfill (Chakra's useMediaQuery calls it on mount), and a jsdom virtualConsole filter that suppresses the "Could not parse CSS stylesheet" noise Chakra triggers per <style> insert.
• .github/workflows/test.yml runs the suite on Node 20 and 24, on push to main and on PR.
• pnpm test, pnpm test:watch added; prepublishOnly now runs the suite too.

Linting

After the initial port, src/tests/ was added to oxlint's ignorePatterns because applying the project's full strict ruleset to upstream-style test code produced ~270 errors. The final commit on this branch reverses that — tests now get linted alongside source, with a scoped override in .oxlintrc.json for the small set of rules that legitimately don't apply to spy/mock-style test code. The vitest plugin is added project-wide (with stylistic preferences disabled). init-declarations ends up off project-wide because it directly conflicts with unicorn/no-useless-undefined and we prefer the latter's style (let captured: T | undefined; over let captured: T | undefined = undefined;).

Test plan

• pnpm lint — passes (4 no-warning-comments warnings for pre-existing project TODOs + upstream-ported // TODO: Cover more scenarios notes; intentional)
• pnpm lint:types — clean
• pnpm test — 271 passed / 4 skipped on both Node 20 and Node 24
• CI workflow ran on push and PR

Out of scope

• Cypress E2E tests (deferred — upstream has 2 specs but they need a running demo page)
• Filling out an even broader chakra-specific suite — current file covers the major user-facing props, but slot-by-slot chakraStyles coverage is incomplete

🤖 Generated with Claude Code

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[pkg-pr-new]

• chakra-react-select-demo

  npm i https://pkg.pr.new/chakra-react-select@412
  

commit: 76d55aa

[github-actions]

📊 Package size report   0.2%↑

File	Before	After
dist/index.js	30.9 kB	0.5%↑31.1 kB
dist/index.mjs	29.4 kB	0.5%↑29.5 kB
package.json	2.8 kB	3%↑2.8 kB
Total (Includes all files)	152.5 kB	0.2%↑152.8 kB
Tarball size	29.9 kB	0.4%↑30.1 kB

Unchanged files

File	Size
dist/index.d.mts	20.1 kB
dist/index.d.ts	20.1 kB
LICENSE.md	1.1 kB
README.md	48.1 kB

_{🤖 This report was automatically generated by pkg-size-action}