Bug: wrong dependency version of @rc-component/util
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 65/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Stale
- Tech stack
- react, typescript
- Domain
- frontend
Research direction
Compare the @rc-component/util dependency in package.json with the useControlledState import in index.tsx. Reproduce the reported Yarn 4 and Vite resolution failure, then verify that the dependency declaration resolves to a util version exporting that hook and that the failing import succeeds.
Written by the indexing model from the issue text.
Description
In index.tsx the following line was introduced:
import { useControlledState } from '@rc-component/util';
this will definitely not fork with util@1.2.1. But ^1.2.1 is defined as dependency in package.json.
In my setup yarn 4.9.2 ant.design transitively resolves so that a local node_modules with util in 1.2.1 is used.
In effect vite resolution fails with lines:
[jc-vue]: ../node_modules/@rc-component/trigger/es/index.js (19:9): "useControlledState" is not exported by "../node_modules/@rc-component/trigger/node_modules/@rc-component/util/es/index.js", imported by "../node_modules/@rc-component/trigger/es/index.js".
[jc-vue]: file: /Users/leider/Dev/JavascriptDev/JC-Backoffice/application/node_modules/@rc-component/trigger/es/index.js:19:9
[jc-vue]:
[jc-vue]: 17: import { getAlignPopupClassName } from "./util";
[jc-vue]: 18: import UniqueProvider from "./UniqueProvider";
[jc-vue]: 19: import { useControlledState } from '@rc-component/util';
[jc-vue]: ^
- Dominant language
- TypeScript
- Stars
- 391
- Forks
- 245
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from react-component/trigger
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
react-component/trigger#623 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
react-component/trigger#618 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
react-component/trigger#555 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
react-component/trigger#550 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
react-component/trigger#495 ·
All issues in react-component/trigger
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100