Tom HT comments

Results 16 comments of


                                            Tom HT

Unable to load @react-aria/textfield as ESM module

Similar issue moving from `@react-aria/utils": "3.11.0` to `@react-aria/utils": "3.11.1` or 3.11.2. It worked fine before, change the version and `import { useId } from '@react-aria/utils'` doesn't work in `ts-node/esm` loader...

Unable to load @react-aria/textfield as ESM module

Had a quick skim over your history for `react-aria/utils` to see what changes might have introduced it - only thing that stands out is upgrading parcel

Unable to load @react-aria/textfield as ESM module

Bump. Any news on this?

Multiple selection support for useComboBox

Is there a way to achieve this behaviour with existing hooks in `react-stately` and `react-aria`? I'm working on a custom component library according to a design system and using `react-aria`...

Is there any way for me to modify the className generation rules

Upvote! We have a problem with the generated classNames in a MFE architecture as our component library is re-imported and so undoes any styled extensions from previously imported MFEs

Bug: Conventional commits do not respect '!' or "BREAKING CHANGE"

> If your package is in major version zero (eg. v0.x.y), the semver rules are shifted over, so breaking changes happen in v0.x.0, and features & patches happen in v0.0.y....

`extensions`: use the `extensionAlias` option of `import-resolver-typescript`

Are there any updates on this?

Support Playwright component testing

Same question

Unexpected input(s) 'script', valid inputs are ['github_token', 'build_script', 'clean_script', 'skip_step', 'directory', 'windows_verbatim_arguments']

Same here

skip_step install not skipping install step

Same here, already installed deps in our job so don't need this auto install - `skip_step: build` should prevent both install and build but both occur and then runs `npx...