61 }
62
63 const updateData = {
64 ...browserLocalData, 65 }
66 updateData.iconStats[watchingStreamer] = newiconStats;
67
66 updateData.iconStats[watchingStreamer] = newiconStats;
67
68 await chrome.storage.local.set(updateData);
69 browserLocalData = await chrome.storage.local.get(); 70 streamerIconStats = browserLocalData.iconStats[watchingStreamer];
71 logger.debug(`update browser local data`, browserLocalData);
72 })
66 updateData.iconStats[watchingStreamer] = newiconStats;
67
68 await chrome.storage.local.set(updateData);
69 browserLocalData = await chrome.storage.local.get(); 70 streamerIconStats = browserLocalData.iconStats[watchingStreamer];
71 logger.debug(`update browser local data`, browserLocalData);
72 })
67
68 await chrome.storage.local.set(updateData);
69 browserLocalData = await chrome.storage.local.get();
70 streamerIconStats = browserLocalData.iconStats[watchingStreamer]; 71 logger.debug(`update browser local data`, browserLocalData);
72 })
73 .catch(err => {
67
68 await chrome.storage.local.set(updateData);
69 browserLocalData = await chrome.storage.local.get();
70 streamerIconStats = browserLocalData.iconStats[watchingStreamer]; 71 logger.debug(`update browser local data`, browserLocalData);
72 })
73 .catch(err => {
Variables that aren't defined, but accessed may throw reference errors at runtime.
Potential ReferenceError
s may result from misspellings of variable and parameter names, or accidental implicit globals (for example, forgetting the var
keyword in a for
loop initializer).
Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a /*global ...*/
comment, or specified in the globals key in the configuration file.
A common use case for these is if you intentionally use globals that are defined elsewhere (e.g. in a script sourced from HTML).
const foo = someFunction();
const bar = a + 1; // 'a' is undeclared
/*global someFunction, a*/
/*eslint no-undef: "error"*/
const foo = someFunction();
const bar = a + 1;