Mark Stacey 2bcb219501 Deobfuscate error message (#10012) ... The SES lockdown added in #9729 had the effect of obfuscating our error messages. Any messages printed to the console would have the error message replaced with the string "Error #" followed by a number. The stack was also updated to point at `lockdown.cjs`, though the original stack was preserved beneath the top stack frame. Marking the `console` API as untamed seems to have fixed both issues. The original error message is now printed to the console, along with the original stack.		2020-12-08 07:24:31 +08:00
..
account-import-strategies
controllers	Initialize network controller provider chainId to the appropriate default networks (#9999)	2020-12-07 11:40:42 -08:00
lib	Remove web3 injection (#9156)	2020-12-07 12:09:02 -08:00
migrations	Migration to remove legacy local storage keys from localStorage (#9986)	2020-12-03 20:25:23 -03:30
platforms
background.js	Add SES lockdown to extension webapp (#9729)	2020-11-24 11:26:43 +08:00
chromereload.js
contentscript.js
first-time-state.js
initSentry.js	Add SES lockdown to extension webapp (#9729)	2020-11-24 11:26:43 +08:00
inpage.js	Remove web3 injection (#9156)	2020-12-07 12:09:02 -08:00
metamask-controller.js	add new MetaMetricsController (#9857)	2020-12-02 15:41:30 -06:00
phishing-detect.js
runLockdown.js	Deobfuscate error message (#10012)	2020-12-08 07:24:31 +08:00
ui.js	Add SES lockdown to extension webapp (#9729)	2020-11-24 11:26:43 +08:00