Wappalyzer: Error throwed in Chrome console after upgrade to 4

[pd4d10]

Uncaught ReferenceError: regeneratorRuntime is not defined
at mobile-c02f111….js:3
at mobile-c02f111….js:3
at mobile-c02f111….js:1

See @malimichael 's reply

[malimccalla]

I'm also having an issues with v4

browser-polyfill.js:590 Uncaught (in promise) 
Object {message: "The message port closed before a response was received."}

[pd4d10]

Sorry for my mistake, error throwed from mobile-c02f111….js has nothing to do with this extension. It's a JS file of website itself.

See @malimichael's reply, same in my browser.

[leadream]

I also have this problem.

[ludwigheymbeeck]

confirmed here as well

[zhaozhiming]

same to me

[AminulBD]

Same problem here.

[TrueMoein]

• same !

[vinioliveira]

Same thing happened to me

[quangvo09]

Same to me

[guanxinHETIC]

+1

[zhonghuiping]

same to me

[themazim]

+1

[amandaluu]

+1

[mitrofun]

+1

[jpmartinezv]

Same to me

[jeeteshnariya]

yaa it's is disable wappalyzer ..! @MannyC

[salmanaligeek]

See this http://imgur.com/LAKGxdL

[emaxedon]

+1

[DaAwesomeP]

This is from the new WebExtension version of the addon. To be clear, are you seeing this error and the extension is not functioning, or are you seeing this error and the extension is still functioning as normal?

In my Chrome, the extension is functioning just fine despite the errors. However, there shouldn't be any errors.

[ssosina]

+1

[serjo96]

same problem

[antwal]

same after upgrade

[aalencar]

same problem here

[develpr]

+1

edit: the extension appears to function correctly, I'm just getting this error, which is a pain for developer tools

[AliasIO]

It's fixed in v4.0.1.

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.