gaearon / gaearon/react-hot-api
Uncaught TypeError: Cannot set property updatePosition
- Dominant language
- JavaScript
- Stars
- 87
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
I meet a strange question and I can't find out the reason. This problem appear after I updated a npm package. Can someone give me some promote?
```
makeAssimilatePrototype.js:21 Uncaught TypeError: Cannot set property updatePosition of # which has only a getter
at patchProperty (webpack:///./~/react-hot-api/modules/makeAssimilatePrototype.js?:21:16)
at eval (webpack:///./~/react-hot-api/modules/makeAssimilatePrototype.js?:52:9)
at Array.forEach (native)
at eval (webpack:///./~/react-hot-api/modules/makeAssimilatePrototype.js?:51:51)
at Array.forEach (native)
at reconcileWithStoredPrototypes (webpack:///./~/react-hot-api/modules/makeAssimilatePrototype.js?:50:21)
at assimilatePrototype (webpack:///./~/react-hot-api/modules/makeAssimilatePrototype.js?:63:5)
at patchReactClass (webpack:///./~/react-hot-api/modules/makePatchReactClass.js?:40:5)
at Object.makeHot (webpack:///./~/react-hot-api/modules/makeMakeHot.js?:33:12)
at makeExportsHot (webpack:///./~/react-hot-loader/makeExportsHot.js?:44:26)
```
My ENV
- node v7.7.3
- npm 4.1.2
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at makeAssimilatePrototype.js:21, where the updatePosition assignment fails, and follow the surrounding calls in the stack trace through react-hot-api. Reproduce it with the listed Node v7.7.3 environment after the npm package update; done means the TypeError is explained and no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, react
- Domain
- frontend, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100