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.

TypeError: e[t] is undefined

See original GitHub issue

Issue Description

Can you describe what steps lead to the error happening? I was on the German homepage (mozilla not allizom) for while (tab in the background) and opened the languages page, on clicking on the link the error page was opened

TypeError: e[t] is undefined
i@https://voice.mozilla.org/dist/bundle.js:1:321
promise callback*G<@https://voice.mozilla.org/dist/bundle.js:61:12401
fi/e<@https://voice.mozilla.org/dist/bundle.js:34:62709
fi@https://voice.mozilla.org/dist/bundle.js:34:62595
Wi@https://voice.mozilla.org/dist/bundle.js:34:78495
$i@https://voice.mozilla.org/dist/bundle.js:34:78872
Na@https://voice.mozilla.org/dist/bundle.js:34:85295
Pa@https://voice.mozilla.org/dist/bundle.js:34:84675
La@https://voice.mozilla.org/dist/bundle.js:34:90886
Tn@https://voice.mozilla.org/dist/bundle.js:34:30451
EventListener.handleEvent*Sn@https://voice.mozilla.org/dist/bundle.js:34:30312
fr@https://voice.mozilla.org/dist/bundle.js:34:37839
qi@https://voice.mozilla.org/dist/bundle.js:34:76511
Wi@https://voice.mozilla.org/dist/bundle.js:34:78567
$i@https://voice.mozilla.org/dist/bundle.js:34:78872
Na@https://voice.mozilla.org/dist/bundle.js:34:85295
Pa@https://voice.mozilla.org/dist/bundle.js:34:84675
xa@https://voice.mozilla.org/dist/bundle.js:34:83696
Ji@https://voice.mozilla.org/dist/bundle.js:34:82599
enqueueSetState@https://voice.mozilla.org/dist/bundle.js:34:47436
E.prototype.setState@https://voice.mozilla.org/dist/bundle.js:26:1652
prepareBundleGenerator/<@https://voice.mozilla.org/dist/bundle.js:61:28251
a@https://voice.mozilla.org/dist/bundle.js:61:26178

Issue Analytics

State:
Created 4 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

Djfecommented, Dec 14, 2018

ok, sounds good. in that case I wouldn’t even inform the user and just reload the frontend upon opening a new page if changes have been detected/if some piece of code gets the info that there is a new version available.

this could be done by letting the user execute the url instead of loading the content only (send true instead of false back to the link)

0reactions

stale[bot]commented, Feb 21, 2022

This issue has been automatically marked as stale because it has not been updated in 2 years. It will be closed if no further activity occurs within the next 30 days.