react-component / react-component/picker
TypeError: Cannot read properties of null (reading 'deoptimizeArgumentsOnInteractionAtPath') when build with vite
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 304
- Forks
- 345
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 7
Description
I use in my project:
"antd": "^5.2.3",
"vite": "^4.1.4",
antd uses "rc-picker": "~3.1.1", under the hood. Current installed version of rc-picker is 3.1.5.
vite uses "rollup": "^3.10.0" under the hood. Current installed version of rollup is 3.19.1.
I use @vitejs/plugin-react (latest 3.1.0 version), except that the build config is default.
When I run vite build I get TypeError: Cannot read properties of null (reading 'deoptimizeArgumentsOnInteractionAtPath').
I added some console.log into deoptimizeArgumentsOnInteractionAtPath to detect the failing module
and got: node_modules/antd/node_modules/rc-picker/es/generate/dayjs.js.
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.
Research direction
Reproduce the failure with vite build using the reported antd, rc-picker, Vite, Rollup, and plugin-react versions. Inspect node_modules/antd/node_modules/rc-picker/es/generate/dayjs.js and the deoptimizeArgumentsOnInteractionAtPath failure; done means the build completes without this TypeError.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, rollup, typescript, vite
- Domain
- build-system, frontend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100