TypeError: item.destroy is not a function
See original GitHub issueHi, I am using vue-lazyload version: 1.3.1 and vue version: 2.6.10.
I am receiving TypeError while using <lazy-component>
:
Uncaught TypeError: item.destroy is not a function
at eval (vue-lazyload.esm.js?0177:1349)
at Array.forEach (<anonymous>)
at Lazy._lazyLoadHandler (vue-lazyload.esm.js?0177:1347)
at runCallback (vue-lazyload.esm.js?0177:484)
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:5
Top Results From Across the Web
Fix the "Uncaught TypeError: destroy is not a function" Error in ...
This React error seems particularly cryptic, but ends up making a lot of sense when you get the hang of the useEffect hook....
Read more >TypeError: destroy is not a function [duplicate] - Stack Overflow
Closed 4 months ago. I am getting this error after using 'useContext(RobinhoodContext)' and importing useContext(that is what I think is going ...
Read more >destroy is not a function...from commitHookEffectListUnmount ...
This error pops up whenever I save to refresh (fast refresh)...it goes away when I make a different change only to re-appear in...
Read more >React — Uncaught TypeError: destroy is not a function - Medium
This function will run when the component unmounts. This can be thought of as roughly equivalent to the componentWillUnmount lifecycle method ...
Read more >destroy is not a function at safelycalldestroy - You.com
Uncaught TypeError: destroy is not a function. It turns out this almost always happens when you try to return anything from your useEffect...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
me too
@hilongjw The fix to this problem is already merged into master. Could you please make a new release, so that all these issues can get resolved?