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 found in settings: ReferenceError: Hints is not defined

See original GitHub issue

Error details

I have next settings in my previous version’s config:

// Hints settings
Hints.characters = "asdfghjkl";
settings.hintAlign = "left";
Hints.charactersUpper = false;

After update to SurfingKeys: 1.0.0 I got “Error found in settings: ReferenceError: Hints is not defined”

SurfingKeys: 1.0.0

Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.198 Safari/537.36

URL: All the sites.


Please replace this with a description of how you were using SurfingKeys.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:4
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

aspierscommented, Dec 29, 2021

I suggest that a rethink of the update process is needed. Realistically, the vast majority users are not going to check release notes for each upgrade - in fact, they won’t even know that an upgrade happened, because the browser does it automatically. So the chances of us finding without being automatically pointed at it are extremely low. That results in most users being caught off-guard by this error, so it is not surprising that there are already multiple duplicate reports of issues relating to this backward-incompatible upgrade (#1576, #1580, and #1574 for a different issue).

Suggested solutions

  1. Avoid backwards-incompatible changes where possible.
  2. Automate the migration of settings from old format to new format.
  3. If 2. is not possible, then gracefully handle those cases with helpful errors which point the user to the migration page, to avoid them having to google for the solution.

Additionally, I suggest making sure that all popup errors from SurfingKeys are clearly labelled as SurfingKeys errors, otherwise it is not at all obvious whether these errors are coming from a browser extension, the browser itself, or the page being visited - and this makes it much harder to figure out the solution.

brookhongcommented, Dec 31, 2021

Since 1.0.2

  • Hints.numericHints = true; was replaced with Hints.setNumeric().
  • Hints.characters = "abcd"; was replaced with Hints.setCharacters("abcd").
Read more comments on GitHub >

github_iconTop Results From Across the Web

Uncaught ReferenceError: wp is not defined, _ is not defined
Hi,. in the browser console i see two errors: Uncaught ReferenceError: wp is not defined and. Uncaught ReferenceError: _ is not defined.
Read more >
ReferenceError- crossfilter is not defined - Stack Overflow
After we updated our d3, dc and crossfilter js files to current, we are getting: crossfilter is not defined error on dc.js (1.7.5)...
Read more >
To v5 from v4 - webpack
But we do list some common advice below regarding Runtime Errors: process is not defined. webpack 5 does no longer include a polyfill...
Read more >
ReferenceError: "x" is not defined - JavaScript - MDN Web Docs
在某些地方引用一个不存在的变量的时候。当你使用变量的时候,这个变量必须是已经被声明的,或者你可以确保它在你当前的脚本或作用域(scope) 中可用。
Read more >
Errors - Akamai TechDocs
The Boomerang Errors plugin automatically captures JavaScript and other ... window.onerror: Uncaught ReferenceError: b is not defined ReferenceError: b is ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Post

No results found

github_iconTop Related Hashnode Post

No results found