Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error relating to vchildren

See original GitHub issue

Context is that we use:

webpack2
webpack-dll
reactrouter
split bundles to deliver react components

page.route.js:168 TypeError: Cannot read property 'vchildren' of undefined
    at destroyVelem (webpack:///./~/react-lite/dist/react-lite.common.js?:363:25)
    at destroyVnode (webpack:///./~/react-lite/dist/react-lite.common.js?:150:9)
    at destroyVelem (webpack:///./~/react-lite/dist/react-lite.common.js?:367:9)
    at destroyVnode (webpack:///./~/react-lite/dist/react-lite.common.js?:150:9)
    at destroyVcomponent (webpack:///./~/react-lite/dist/react-lite.common.js?:492:5)
    at destroyVnode (webpack:///./~/react-lite/dist/react-lite.common.js?:153:9)
    at destroyVcomponent (webpack:///./~/react-lite/dist/react-lite.common.js?:492:5)
    at destroyVnode (webpack:///./~/react-lite/dist/react-lite.common.js?:153:9)
    at destroyVcomponent (webpack:///./~/react-lite/dist/react-lite.common.js?:492:5)
    at destroyVnode (webpack:///./~/react-lite/dist/react-lite.common.js?:153:9)

Issue Analytics

State:
Created 7 years ago
Comments:14 (9 by maintainers)

Top GitHub Comments

1reaction

Lucifier129commented, Apr 6, 2017

For keeping small, we are not going to handle the practice which is not recommended or unexpectedly, react-lite just follow the best-practice of react 😉

0reactions

zemajcommented, Apr 11, 2017

Thanks Matt!

I’d love to see this merged. It’s a very lightweight solution to a complex problem.

We don’t always have control over the environments our apps run in. react fails gracefully in this situation and many people are going to encounter this problem when they switch from react to react-lite

On 11 April 2017 at 10:13, Matt notifications@github.com wrote:

@zemaj https://github.com/zemaj @Lucifier129 https://github.com/Lucifier129 Please see my fork #108 https://github.com/Lucifier129/react-lite/pull/108 that resolves this issue.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Lucifier129/react-lite/issues/90#issuecomment-293113699, or mute the thread https://github.com/notifications/unsubscribe-auth/AABwv5wmoUAysjldgtEWNXMapT0a2DeIks5rusWdgaJpZM4LQD0t .

– James Peter ChargeDesk CEO & Co-Founder +1 (650) 741-4677